Allows exporting a manifest that maps entry chunk names to their output files, instead of keeping the mapping inside the webpack bootstrap.
Switch branches/tags
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib Fix regression in 1.1.1 (#44) Jul 26, 2017
.gitignore Initial commit Aug 22, 2014 Version bump Apr 21, 2017 Initial commit Aug 22, 2014 Updated examples to es6 (#22) Apr 24, 2017
package-lock.json Add package-lock.json Aug 1, 2018
package.json 1.1.2 Jul 26, 2017


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.


Install via npm:

npm install --save-dev chunk-manifest-webpack-plugin

Install via yarn:

yarn add --dev chunk-manifest-webpack-plugin

And then require and provide to webpack:

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

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



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


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


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

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