bug with require

[bobrik]

I've got a strange behavior with require when in some cases require() at the beginning of the file causes undefined instead of contents of exports object. Lazy require in methods works well in that case (I really hope so).

You may see example code here: node-require-bug.

Sorry for my poor English explanation, I hope you'll see everything in example.

[kurokikaze]

Strange behavior. When you move require('UserFactory') inside getAdminUser functtion body, it works.

[bobrik]

yep, that's my hack for now. But I suppose there may be some troubles too

[isaacs]

This is by design.

When you have circular require() calls, a module might not be done being executed when it is returned.

Consider this:

// a.js
console.log("a starting")
exports.done = false
var b = require("./b.js")
console.log("in a, b.done = %j", b.done)
exports.done = true
console.log("a done")

// b.js
console.log("b starting")
exports.done = false
var a = require("./a.js")
console.log("in b, a.done = %j", a.done)
exports.done = true
console.log("b done")

// main.js
console.log("main starting")
var a = require("./a.js")
var b = require("./b.js")
console.log("in main, a.done=%j, b.done=%j", a.done, b.done)

$ node main.js 
main starting
a starting
b starting
in b, a.done = false
b done
in a, b.done = true
a done
in main, a.done=true, b.done=true

Todo: Add this to the module docs.

[kurokikaze]

Thanks for clarifications :)