node cached export object is broken

I'm requiring an module that has already been required in another file, but when I get the object, many of it's keys are undefined. A bunch of the keys are there, but some are not, even after I call some of the exposed functions. If I console.log the object, the keys look like they are there.

Example:

var mod = require('myModule')
console.log(mod) // { 'aKey':[Function], 'doStoff':[Function] }
console.log(mod.aKey) // undefined
mod.doStoff() // calls 'aKey' 
//TypeError: Object #<Object> has no method 'aKey'
//this error is thrown inside myModule

This would not overly surprise me if this module was doing something goofy when it get's loaded, but the module has already been loaded and I have used it for several things already in the main js file.

The only thing I can think of that is off the norm: I've required this module in the main js file (and it works), but the place that it does not work is inside a module that is required in the main.

To be clearer->

• main.js requires myModule
• main.js requires otherModule
• otherModule requires myModule

myModule was installed by npm, but I'm prototyping the otherModule in place in the node_modules folder until I get it put up somewhere so npm will install it.

I don't see why this would cause a problem; I thought that the object that gets returned from require gets kept in the require cache--as is--so that when it gets required any time afterwards you get that same object. It seems that my object has been partially deleted or something.

What is causing this? What should I do differently?