-
Notifications
You must be signed in to change notification settings - Fork 94
doesn't work with webpack-manifest-plugin #32
Comments
I can try to figure it out, but since both of them use the I'll keep this issue under discussion. |
I'm using Webpack 4.3. The generated manifest file indeed appears in the asset manifest file, but the key is invalid, should be:
but is instead
meaning it's not valid and I cannot use it. Don't know which plugin is responsible for this though :( |
To fix the problem described by @mikemix I use the ...
.configureManifestPlugin((options) => {
options.map = (file) => {
if (/^build\/webmanifest\..+\.json$/.test(file.name)) {
file.name = 'build/webmanifest.json';
}
return file;
};
})
... (Note this is webpack encore, not a pure webpack config...) |
Have the same issue with webpack 4.46.0 |
webpack-manifest-plugin is plugin for creating assets manifest.
It creates JSON file with a mapping of all source file names to their corresponding output file.
But manifest created with
webpack-pwa-manifest
not appear in assets manifesti think it's related to shellscape/webpack-manifest-plugin#102 (comment)
but maybe it can be solved from side of
webpack-pwa-manifest
?The text was updated successfully, but these errors were encountered: