chunk-manifest-webpack-plugin

Allows exporting a manifest that maps chunk ids to their output files, instead of keeping the mapping inside the webpack bootstrap.

1.1.0
Source
npm

Version published: 8 years ago

Maintainers: 1

Created: 10 years ago

Source

chunk-manifest-webpack-plugin

Allows exporting a JSON file that maps chunk ids to their resulting asset files. Webpack can then read this mapping, assuming it is provided somehow on the client, instead of storing a mapping (with chunk asset hashes) in the bootstrap script, which allows to actually leverage long-term caching.

Usage

Install via npm:

npm install chunk-manifest-webpack-plugin

Install via yarn:

yarn add chunk-manifest-webpack-plugin

And then require and provide to webpack:

// in webpack.config.js or similar
var ChunkManifestPlugin = require('chunk-manifest-webpack-plugin');

module.exports = {
  // your config values here
  plugins: [
    new ChunkManifestPlugin({
      filename: "manifest.json",
      manifestVariable: "webpackManifest",
      inlineManifest: false
    })
  ]
};

Options

`filename`

Where the manifest will be exported to on bundle compilation. This will be relative to the main webpack output directory. Default = "manifest.json"

`manifestVariable`

What JS variable on the client webpack should refer to when requiring chunks. Default = "webpackManifest"

`inlineManifest`

Whether or not to write the manifest output into the html-webpack-plugin. Default = false

// index.ejs
<body>
    <!-- app -->
    <%= htmlWebpackPlugin.files.webpackManifest %>
</body>

Keywords

FAQs

What is chunk-manifest-webpack-plugin?

Is chunk-manifest-webpack-plugin well maintained?

Package last updated on 24 Apr 2017

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install