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
<body>
<!-- app -->
<%= htmlWebpackPlugin.files.webpackManifest %>
</body>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4