behaviour of circular dependencies in resolving node.js modules

I was reading the Node.js design patterns book when I came across this section of cycles in module resolution. This is the sample code: Module a.js: exports.loaded = false; var b = require('./b'); module.exports = { bWasLoaded: b.loaded, load...