require-context v1.1.4

changes: this version supports a directory or an array of directories (which, yes, is dangerous because of collisions. but useful for submodules in some contexts)

Installation

Using npm:

1$ npm i -g npm
2$ npm i --save require-context

In Node.js:

1// Load globally into all modules.
2require('require-context/register')
3
4// Load locally as a function.
5var requireContext = require('require-context');

Usage

It allows you to pass in a directory to search, a flag indicating whether subdirectories should be searched too, and a regular expression to match files against.

The syntax is as follows:

1require.context(directory, useSubdirectories = false, regExp = /^\.\//)

Examples

1require.context("./test", false, /\.test\.js$/);
2// a context with files from the test directory that can be required with a request endings with `.test.js`.

1require.context("../", true, /\.stories\.js$/);
2// a context with all files in the parent folder and descending folders ending with `.stories.js`.

Context API

A context module exports a (require) function that takes one argument: the request.

The exported function has 3 properties: resolve, keys, id.

• resolve is a function and returns the module id of the parsed request.
• keys is a function that returns an array of all possible requests that the context module can handle.

This can be useful if you want to require all files in a directory or matching a pattern, Example:

1function importAll (r) {
2  r.keys().forEach(r);
3}
4
5importAll(require.context('../components/', true, /\.js$/));

Why require-context?

• Take the hassle out of requiring groups of modules
• Write cross-platform code between webpack and node