chunk-manifest-webpack-plugin
Version:
Allows exporting a manifest that maps chunk ids to their output files, instead of keeping the mapping inside the webpack bootstrap.
57 lines (40 loc) • 1.47 kB
Markdown
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:
```shell
npm install --save-dev chunk-manifest-webpack-plugin
```
Install via yarn:
```shell
yarn add --dev chunk-manifest-webpack-plugin
```
And then require and provide to webpack:
```javascript
// 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](https://github.com/ampedandwired/html-webpack-plugin). Default = `false`
```html
// index.ejs
<body>
<!-- app -->
<%= htmlWebpackPlugin.files.webpackManifest %>
</body>
```