Closed aldeka-humu closed 4 years ago
Hey all! I've taken over maintenance of the plugin and am doing some housecleaning. If the issue is still pending and still a problem, please reply with a reproduction and we'll reopen post-haste.
Please provide a reproduction by choosing one of the options below:
Provide a minimal repository link (Read https://git.io/fNzHA for instructions). Please use NPM for installing dependencies! These may take more time to triage than the other options.
⚠️ ZIP Files are unsafe and maintainers will NOT download them.
I installed webpack-manifest-plugin and added it to my webpack config plugins list without any configuration--it's just
new ManifestPlugin()
.ManifestPlugin outputs the following manifest for this code base:
You'll note that the files have /dist/ and a release number folder prepended to their path, with the release number changing every time a build is run. This does not match the actual webpack output! See screenshot:
(The actual file names and their hashes are correct, however.)
In the docs I see ways to prepend folders onto the path if so desired, but that's not supposed to be the default behavior. The documented behavior is that the output files and the manifest paths should match, and they very much don't.
FWIW I'm using webpack 4.x and webpack-manifest-plugin 2.2.0.