node-require-directory icon indicating copy to clipboard operation
node-require-directory copied to clipboard

Recursively iterates over specified directory, requiring each file, and returning a nested hash structure containing those libraries.

Results 18 node-require-directory issues
Sort by recently updated
recently updated
newest added

Might make sense to put one in the README?

Support for requiring TypeScript files was missing.

After running the webpack package file, an exception 【throw new ERR_INVALID_ARG_TYPE(name, 'string', value)】 is thrown, causing the file to fail to run.

This will help us in debian packaging as we take the source directly from github.

Hi I am pretty new to node. After changing module file extensions from ".js" to ."mjs" and adding -r esm arguments to node, I am getting error "module" is not...

As this package is used by [yargs](https://github.com/yargs/yargs) in the [`.commandDir()` function](https://github.com/yargs/yargs/blob/master/docs/advanced.md#commanddirdirectory-opts) ([there](https://github.com/yargs/yargs/blob/master/lib/command.js#L109)) , I'd like to be able to require js files with no extension. Since it doesn't necessarily reflect...

I would need to load module with: ``` export default function () {} ```

There are no definitions for TS users for this project anywhere - I think they'll provide better developing experience. If needed I can add JSDocs to this definitions too.

If a directory contains a broken symlink at any level of its subdirectory tree, performing `require-directoty()` in it will always throw an ENOENT error. For example, running `index.js` in the...