node-require-directory
node-require-directory copied to clipboard
troygoode
Recursively iterates over specified directory, requiring each file, and returning a nested hash structure containing those libraries.
It seems possible, all we need to do is: 1. watch for changes in the dir 2. re-`require` any changed or new files 3. replace or add to the object...
What about using [parent-module](https://www.npmjs.com/package/parent-module) or directly [callsites](https://www.npmjs.com/package/callsites) to avoid the need of passing `module` as the first argument?
proposal is to pass path and basename as such: ``` check = function(filepath, filename) { ... } // where filename = require("path").basename(filepath) ``` `module.exports = requireDirectory module, exclude: check`
perhaps allow recurse to be provided as an integer which gets decremented every time we recurse so that we can limit the levels we descend, instead of just true/false?
Hello! Thank you for this great module! However, consider please the following scenario: - config/integration.js - config/integration/facebook.js - config/integration/google.js - config/integration/twitter.js ``` javascript // integration.js module.exports = { timeout: 30000,...
`include-folder` works with browserify (via `folderify`), but doesn't iterate recursively. `node-require-directory` works recursively, but I'm not sure how to make it work with browserify. Is there a browserify plugin for...
