extended-require v1.2.0

Extended Require for Node.JS

Extends require() capabilities.

Installation

You can install with npm:

npm install extended-require

Usage

/path/to/project/index.js :

var er              = require("extended-require");
var extendedRequire = er.require;

// creates a new include path set
// only files under /path/to/project/lib will use that include path set
// you can create as many include path sets as you want
var includePath = er.newIncludePath("lib");

// add /path/to/project/lib to the include path
includePath.add(".");

// add /path/to/project/lib/other/dir to the include path
includePath.add("other/dir");

// ......

// will try to load in order (stops on the first found file/dir) :
// - /path/to/project/lib/dir/file
// - /path/to/project/lib/dir/file.js
// - /path/to/project/lib/other/dir/file
// - /path/to/project/lib/other/dir/file.js
// if none of these paths exists, "dir/file" is forwarded as is to the builtin require() function
var file = extendedRequire("dir/file");

// you can use the bind() function as well
extendedRequire.bind(extendedRequire, "dir/file");

API

newIncludePath({string} rootDirectory , {string} id)

Creates a new include path set. The rootDirectory arg can be absolute or relative to the file that call it. This arg is used to filter include path sets. For example, if you set it to /path/to/dir, only files that resides into that directory will use that include path set on a call to require(). For files that are outside that directory, this include path set will be ignored.

If the optional id arg is given, it will be set as the identifier of the include path set created.

Returns an instance of IncludePath.

resetIncludePathList()

Discards all include path sets.

require({string|Array} path , {boolean} fallbackToBuiltin)

Requires a module using defined include path sets.

The path arg is the path to the module to be loaded and can be absolute or relative to one of include paths. An include path set id can be specified as an array, in the form [id, path]. In that case, only the include path set referenced by this identifier will be used, and no check of the include path set root directory will be performed.

Example :

/path/to/project/index.js :

var er              = require("extended-require");
var extendedRequire = er.require;

var includePath1    = er.newIncludePath("lib", "id1");
var includePath2    = er.newIncludePath("other/dir", "id2");

// might be /path/to/project/lib/file.js or /path/to/project/other/dir/file.js
var file1 = extendedRequire("file.js");

// might be only /path/to/project/other/dir/file.js
var file2 = extendedRequire(["id2", "file.js"]);

The fallbackToBuiltin arg indicates if the path arg has to be forwarded to the builtin require() function in case no include path set satisfies required path. Defaults to true. If an include path set id is specified, fallbackToBuiltin is always false.

IncludePath object

IncludePath.add({string} path)

Adds an include path to the include path set. The path arg is always relative to the root directory of the include path set. Note that only paths added with the add() method will be used to require files/dirs (the root directory is only used as a filter). To include the root directory itself, use includePath.add('.').

IncludePath.getRootDirectory()

Returns the root directory of the include path set.

IncludePath.reset()

Resets the include path set (the root directory is preserved).

IncludePath.isInRootDirectory({string} path)

Indicates if the path arg is in the root directory of the include path set. path must be absolute;

IncludePath.resolve({string} path)

Resolves a path. If the path is a JavaScript file, the '.js' extension can be omitted. The path is appended to each include path in the order they have been declared, and the resulting absolute path is returned as soon as it exists on the filesystem. Returns null if no file were found. path is alwayd considered a relative path.

Configure automatically

You can save you the effort to programmatically configure include path sets by adding them to your package.json.

{
    // ...
    "extended-require": [
        // first include path set
        {
            "rootDirectory": ".", // required
            "id": "idtest", // optional
            "include-path": ["lib", "other/dir"] // required
        },
        // second include path set
        {
            "rootDirectory": "sub/dir",
            "include-path": ["sublib"]
        }
    ]
}

• The rootDirectory parameter defines the root directory of the include path set. It can be absolute or relative to the package.json file.
• The id parameter defines the include path set identifier and is optional.
• The include-path parameter defines include paths.

The above example is equivalent to :

// lib/index.js

var er = require("extended-require");

var includePath1 = er.newIncludePath("..", "idtest");
includePath1.add("lib");
includePath1.add("other/dir");

var includePath2 = er.newIncludePath("sub/dir");
includePath1.add("sublib");

When you call the module's require() function, the closest package.json is loaded and include path sets it contains are configured. The closest package.json is first searched in the directory containing the file that called the module's require() function, then its parent directory, and so on until a package.json file is found or the file system root directory is reached.

Note: you don't need a package.json. If you don't have one, no error is thrown.

Note 2: if you don't want to put any include path set in your package.json, don't include a extended-require key!

Author

This project is authored and maintained by Stephen Berquet.

License

Licensed under the MIT License - see the LICENSE file for details