context-map-webpack-plugin weekly downloads statistics

context-map-webpack-plugin

Webpack plugin to map dynamic (thirdparty) dependencies to a static context map.

Install

Why do I need it / What does it do?

The Problem

Some (thirdparty) code requires other files with expressions that cannot be resolved by webpack at compile-time. Webpack tries to generate a regular expression that determines which files to include in the webpack bundle. In more complex expressions, webpack is unable to determine which files to include, thus an empty context map will be created.

A dynamic import that cannot be resolved might look like this:

Your webpack build will probably have this Critical dependency warning:

This will result in a bundle output that looks like this:

This empty context will lead to runtime errors:

The Solution

Create a static context map in compile-time in order to include all required dependencies. You are required to investigate all possible runtime values of the required argument where the error originates from. These values have to be passed as the staticImports argument in the plugin constructor.

Alternatives

If you use webpack for the backend, you can exclude the required files from the webpack bundle and depend on node_mdules by using webpack-node-externals.

Usage

In your webpack configuration:

Parameters

contextPath

• Type: String • Default: undefined

Specify the directory in which to create/overwrite the context map.

staticImports

• Type: Array[String] • Default: undefined

Static imports that will be written to the context map (and bundled with webpack at compile-time).

Example (uglify-js)

License

MIT

Description from the npm listing.