The answer
Use delete require.cache[require.resolve('./file')] to remove the cached module, forcing it to reload on the next require. This is rarely needed in production but useful in testing and development.
Node.js Module Caching Explained: How require Caches Modules
How do I clear the Node.js module cache?
More FAQs in Node.js Module Caching Explained: How require Caches Modules
When you require a file, Node.js runs it once and stores its module.exports in a cache. Subsequent requires of the same file return the cached object without running the file again, so a module's code runs once.
Because it means a module's code runs once, and every file that requires it sees the same value. This is useful for shared state like database connections and configuration, and enables the singleton pattern without extra code.
Yes. A module that exports a single object acts as a singleton, since every require returns the same cached instance. This is how shared database connections and configuration work in Node.js apps.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.