A common pattern in node.js is to include an index file which creates a hash of the files in its current directory. Given a directory structure like so:
*Note that `routes.index` will be `undefined` as you would hope.*
### Specifying Another Directory
You can specify which directory you want to build a tree of (if it isn't the current directory for whatever reason) by passing it as the second parameter. Not specifying the path (`requireDirectory(module)`) is the equivelant of `requireDirectory(module, __dirname)`:
```javascript
var requireDirectory = require('require-directory');
module.exports = requireDirectory(module, './some/subdirectory');
```
For example, in the [example in the Usage section](#usage) we could have avoided creating `routes/index.js` and instead changed the first lines of `app.js` to:
```javascript
var requireDirectory = require('require-directory');
var routes = requireDirectory(module, './routes');
```
## Options
You can pass an options hash to `require-directory` as the 2nd parameter (or 3rd if you're passing the path to another directory as the 2nd parameter already). Here are the available options:
### Whitelisting
Whitelisting (either via RegExp or function) allows you to specify that only certain files be loaded.
```javascript
var requireDirectory = require('require-directory'),
check = function(path){
if(/dontinclude\.js$/.test(path)){
return false; // don't include
}else{
return true; // go ahead and include
}
},
hash = requireDirectory(module, {exclude: check});
```
### Visiting Objects As They're Loaded
`require-directory` takes a function as the `visit` option that will be called for each module that is added to module.exports.
```javascript
var requireDirectory = require('require-directory'),
visitor = function(obj) {
console.log(obj); // will be called for every module that is loaded
},
hash = requireDirectory(module, {visit: visitor});
```
The visitor can also transform the objects by returning a value: