The smart way of requiring many files
npm install require-smart[![Build Status][build-status-image]][build-status-url] [![Dependency Status][dependencies-image]][dependencies-url]
The smart way of organizing your app's files and folders, by requiring recursivelly and automagicly parsing file names as their scope key.
[build-status-image]: https://img.shields.io/travis/ivanseidel/node-require-smart.svg
[build-status-url]: http://travis-ci.org/ivanseidel/node-require-smart
[dependencies-image]: https://gemnasium.com/badges/github.com/ivanseidel/node-require-smart.svg
[dependencies-url]: https://gemnasium.com/github.com/ivanseidel/node-require-smart
[npm-image]: https://nodei.co/npm/require-smart.png?downloads=true&stars=true
[npm-url]: https://nodei.co/npm/require-smart
```
$ npm install require-smart
This library was created for three main reasons:
1. Avoid requiring an obvious object tree within each file
2. Encourage files with minimum number of business logic
3. Allow filenames to be more clear on what they do
`javascript
const RequireSmart = require('require-smart')
const myModules = RequireSmart('./myModulesFolder')
`
You might have this folder structure:
``
controllers
├─ users.js
├─ users.login.js
├─ users.create.js
├─ users.delete.js
├─ users.update.js
├─ queue.opts.default.js
└─ some_other.arbitrary-name.thing.js
Or maybe this folder structure:
``
controllers
├─┬ users/
│ ├─ index.js
│ ├─ login.js
│ ├─ create.js
│ ├─ delete.js
│ └─ update.js
├─┬ queue/
│ └─ opts.default.js
└─┬ some_other/
└─┬ arbitrary-name/
└─ thing.js
Or even an merged style:
``
controllers
├─┬ users/
│ ├─ index.js
│ ├─ login.js
│ ├─ create.js
│ ├─ delete.js
│ └─ update.js
├─ queue.opts.default.js
└─┬ some_other.arbitrary-name/
└─ thing.js
You will get an object required like this:
`javascript
{
users: {
... require('./users/index'), [ Gets Merged ]
login: require('./users/login'),
create: require('./users/create'),
delete: require('./users/delete'),
update: require('./users/update')
},
queue: {
opts: {
default: require('./queue.opts/default')
}
},
someOther: {
arbitraryName: require('./some_other.arbitrary-name/thing')
}
}
`
You can customize the way RequireSmart loads your dependencies.
- depth: [Default: true]false
If set to , will not load folders recursivelly. If set to a Number, Will load until that depth. Set to true for infinite recursion on requirecanMerge
- : [Default: true]false
If set to , will throw exception if a object merge is neededindexNames
- : [Default: ['index']]index
Set the array of name without extensions of 'file indexes' (usually only)extensions
- : [Defaults: ['.js', '.json']]fileNameSeparator
Sets the valid extensions to be required
- : [Defaults: .]uppercaseTokens
What token to use as separator of file names.
- : [Defaults: /[_\s-]]\w/g]
A regex that maches the separation, and the first character of the next word
$3
If you desire to view what are the steps to be performed during the require, you can use the method view:
`javascript`
RequireSmart.view(__dirname + '/myModulesPath')
It will print out for each one of the files, the destination hash on the object, and also if it
will get merged or set. npm install chalk` to view output with colors.
Use this library as close to the top of your application. This is something really usefull
for loading controllers, helpers, models, modules, wales and cats. However, you should use
this with care.
If you are building a Library or maybe something that the user (and not you) might have controll,
be aware of the power you might be giving him. Think about security. Again.