javascript - Module.export-ing a New Instance - Stack Overflow

admin管理员组

文章数量:1345080

If I attach an object to the module.exports object in node like so:

module.exports = new Object()

will each object = require('./Object') throughout my application create a new instance of that object, or will it create a reference to the one instance?

If I attach an object to the module.exports object in node like so:

module.exports = new Object()

will each object = require('./Object') throughout my application create a new instance of that object, or will it create a reference to the one instance?

• javascript
• node.js
• monjs

Share Improve this question Follow asked Sep 9, 2013 at 0:21 Connor BlackConnor Black 7,1811212 gold badges4040 silver badges7171 bronze badges 1

• 2 If you want a new instance for each use, it's probably worth making each create their own instance. module.exports = Object; then var Object = require('./Object'), object = new Object();. – Jonathan Lonowski Commented Sep 9, 2013 at 0:47

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 10

require() caches files that it executes.

The first time you require('./Object'), it will run your code and place the exported object in require.cache.
Subsequent calls will return the cached object immediately.

You could remove your module from the cache yourself, or use a getter, but those are bad ideas.

Check out caching caveats in the node docs. You'll get the same object as long as the resolved module path matches. There's an example in this answer of when resolved paths would not match.

本文标签： javascriptModuleexporting a New InstanceStack Overflow