In this lesson, you will learn how Node.js remembers your modules after the first time they are loaded to boost performance and how you can override this behavior when testing.
The Power of the Cache
When you require or import a file in Node.js, the runtime performs a series of steps: it searches for the file, resolves its absolute path, reads the code, and executes it. Because this process involves looking through your file system—which is relatively slow—Node.js caches the result.
Once a module is loaded, Node.js stores its exports object in a special internal object called require.cache. The next time you call require('./myModule'), Node.js skips the disk lookup and execution phase entirely, instantly returning the reference from the cache.
Why Cache Invalidation Matters
In a production environment, this is a huge performance win. However, it can become a headache during unit testing. If you are testing a module and want to verify how it behaves with different internal states or different external configuration files, the cache will block you by serving the first version it loaded.
To test these scenarios, you must manually invalidate the cache. You can do this by deleting the specific entry from the require.cache object using the file’s resolved path:
// Manually deleting a module from the cache
const path = require.resolve('./myModule');
delete require.cache[path];
// The next require will re-load the file from disk
const freshModule = require('./myModule');
By deleting the entry, you force Node.js to treat the module as if it were being loaded for the very first time.
A Note on Best Practices
While clearing the cache is essential for specific testing patterns, you should avoid doing this in your main application logic. The module loader relies on the caching mechanism to maintain a "singleton" pattern for your modules, ensuring that all parts of your application share the same state. Modifying the cache globally can lead to unexpected bugs where different parts of your code hold onto different versions of the same dependency.
Key Takeaway: Node.js caches modules after the first load to optimize performance, but you can force a re-load by deleting the module's path from the require.cache object during testing.