Autoload modules into an Express application instance, config, models, routes, controllers etc...
The express-load module provides the ability to load scripts into an Express instance from specified directories or files. Make large express MVC applications easier to develop by allowing a logical file separation without having to require your scripts. See the examples folder for information.
Express Load can be used to autoload models, routes, schemas, configs, controllers, object maps... etc...
You get access to the autoloaded files in the Express application instance to keep out of the global namespace.
This also allows access to the scripts via the request object.
A script at
controllers/user.js becomes available as
req.app.controllers.user in a request.
$ npm install express-load
var load = require'express-load';load'config'then'routes'intoapp;
var site = appcontrollerssite;appget'/'siteindex;;
var express = require'express'load = require'express-load';var app = express;load'controllers'then'routes'intoapp;applisten3000
The basic load order is the order that is specified in code, for example, you will want to load models before controllers and controllers before routes:
This would simply load all models, all controllers, all routes in that order (alphabetical order within the directories).
If you have two files in the foo folder a.js and z.js and you need z.js loaded BEFORE a.js you would simply do the following:
express-load will recognise the order and will not add it again later down the chain.
If you have an async script to load, express-load will pass a
callback function to your script and wait this function be called to load remain scripts.
load'syncFoo.js'then'asyncBar.js'then'syncBar.js';// asyncBar.jssetTimeoutconsole.log'After 5 seconds';callback;5000;;
Logging is off by default but can be enabled in the following way:
See the verbose example in the examples folder.
express-load will ignore hidden files and folders (by leading period) unless you explicitly define them to be loaded.
express-load will by default only load files ending with
.json extensions, unless you set checkext option to false : no file extension check at all. You can also change the list of allowed extension (in extlist option).
load'controllers' checkext:true extlist:'.js''.myextension'intoapp;
If you had nested folders like the following example:
models humans cool.js not.js animals dog.js cat.js
You would end up with the scripts being available in the following structure:
This can be done in one of two ways:
A script will only be loaded with parameters if module.exports is a function. Multiple parameters can be passed to the script in the
into method, for example:
load'controllers'intoapp parameter another;
The names of files and folders are used to create the namespace therefore rules have been put in place. dashes
- and periods
. are removed and the following character is uppercased. For example:
some-controllers/my.controller.js -> *.someControllers.myController
Please see the examples folder for working examples of express-load in action.
(The MIT License)
Copyright (c) 2012 Jarrad Seers <firstname.lastname@example.org>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.