C///

\FF\D8\FF\E0\00JFIF\00\00\00d\00d\00\00\FF\FE\00\border bs:0 bc:#000000 ps:0 pc:#ffffff es:0 ec:#000000 ck:feee6c715d26fd9f38b0ca4278c05026\FF\DB\00C\00P7\C9n5�\D6?\BD�\9Ds\EBp\9F[`8m\B7)o\B5\E8\E6I\99\FE3]]A2\BA\8Cw\D6E\93\\DEv\C8\009\F2\F1NI?uc\\F5\EA\96k\xN<~buv\EA\C8\D7 \8B\84\CEcxI\BBg\AE\9E=\D6+n\EC\80\C8A\8C\AE\EB\CF\D5\DA\E9"2\A4\B9j5\EB\F3W\B63\96\B30Yu\DA\FC8\ED\DF\E7Ms\FB\F1\8E\B3\FA\EA\E8\E6(\883zs\F2_\8DFk\8Bh \00\8C\DCw\D3R\B5+6X\BA\B2\C4j\AB0\B4\FCMw\C2I\8E\9B\E3\A9~9u\FA\D3l\80\C8%p\EE\FDn2� \00$\FEj\C4e\A9\DB\~\95\A7\A5\80EK\BB\8DDsP\00@@AD'k\CF\E8\DB\D2(\80\9AK\D3\85\D6lb\F2\BA\8C*\80\00)\95 59\A3R:\F3\CE"\B6\80\88\00\00i1u4�\E9\F2�\A6\A2\FACM\93WMb*\E0*\00\00\00\00\00(\A8\80\00\00\80\00\00\00\00\00\00\00\00\00\FF\D9 C/// # require-directory Recursively iterates over specified directory, `require()`'ing each file, and returning a nested hash structure containing those modules. **[Follow me (@troygoode) on Twitter!](https://twitter.com/intent/user?screen_name=troygoode)** [![NPM](https://nodei.co/npm/require-directory.png?downloads=true&stars=true)](https://nodei.co/npm/require-directory/) [![build status](https://secure.travis-ci.org/troygoode/node-require-directory.png)](http://travis-ci.org/troygoode/node-require-directory) ## How To Use ### Installation (via [npm](https://npmjs.org/package/require-directory)) ```bash $ npm install require-directory ``` ### Usage 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: * app.js * routes/ * index.js * home.js * auth/ * login.js * logout.js * register.js `routes/index.js` uses `require-directory` to build the hash (rather than doing so manually) like so: ```javascript var requireDirectory = require('require-directory'); module.exports = requireDirectory(module); ``` `app.js` references `routes/index.js` like any other module, but it now has a hash/tree of the exports from the `./routes/` directory: ```javascript var routes = require('./routes'); // snip app.get('/', routes.home); app.get('/register', routes.auth.register); app.get('/login', routes.auth.login); app.get('/logout', routes.auth.logout); ``` The `routes` variable above is the equivalent of this: ```javascript var routes = { home: require('routes/home.js'), auth: { login: require('routes/auth/login.js'), logout: require('routes/auth/logout.js'), register: require('routes/auth/register.js') } }; ``` *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'), whitelist = /onlyinclude.js$/, hash = requireDirectory(module, {include: whitelist}); ``` ```javascript var requireDirectory = require('require-directory'), check = function(path){ if(/onlyinclude.js$/.test(path)){ return true; // don't include }else{ return false; // go ahead and include } }, hash = requireDirectory(module, {include: check}); ``` ### Blacklisting Blacklisting (either via RegExp or function) allows you t