Custom Require
With this module you can receive a callback for any non-native dependecies an specific module loads, including the dependencies of his dependencies, and so on.
To check for module and dependencies modifications, see https://github.com/Llorx/watcher-require
To always receive an updated version of your modules, checking files and dependencies modifications, see https://github.com/Llorx/updated-require
Installation
npm install custom-require
Usage
/* FILE: test1.js */// Load any non-native module; moduleexports = "yay";
/* FILE: test2.js */// Load any non-native module;;
/* FILE: main.js */// Load the module at the top of the entry point filevar CustomRequire = CustomRequire; // If you are using TypeScript, you can use import; // Instantiate an object with a callback that will be called when a module is loadedvar firstWalker = { console;}; // Require a module to see its dependenciesfirstWalker; // You can also require another file. Already called dependencies will not be called againfirstWalker; // You can create different Custom Require instances together in the same scriptvar secondWalker = { console;}; // Requiring modules already required by another instance will not be a problem// Second walker will receive all the dependencies too// The require method will work as the default require one, returning the exports contentsvar yay = secondWalker; // Yay itconsole; // After you have finished, call dispose() to clean resources attached to modulesfirstWalker;secondWalker;
Also, it works with asynchronous requires
/* FILE: async_test.js */// Load any non-native module;;
Limitations
As the nature of Node.js, required modules are cached, so doing this will not work as expected:
// Load the test module before the Custom Require; // Now load Custom Requirevar CustomRequire = CustomRequire; // And make an instancevar walker = { console;}; // This will show redux dependencies, but not react ones as they were loaded before Custom Requirewalker;
Custom Require will be only able to track modules loaded after it has been required for the first time, so is recommendable to require it at the top of the entry-point file. Is not needed to add it to each file. Only at the entry-point.
NOTE: Custom Require will start tracking right after requiring it. Is not necessary to immediately create an instance.