assets-webpack-plugin
assets-webpack-plugin copied to clipboard
Webpack plugin that emits a json file with assets paths
__IMPORTANT: Please do not create a Pull Request without creating an issue first.__ _Any change needs to be discussed before proceeding. Failure to do so may result in the rejection...
**Describe the bug** On the previous version: ``` webpack: 4.46.0 assets-webpack-plugin: 5.1.1 compression-webpack-plugin: 5.0.0 ``` The output gzips from `compression-webpack-plugin` were added to `assets.json`, ex: ``` { "main": { "js":...
Got the same problem as described [here](https://github.com/ztoben/assets-webpack-plugin/issues/312), but with v7.1.1. Had to downgrade to 7.0.0. It's important for my project to have access to the emitted files in `processOutput` because...
**Is your feature request related to a problem? Please describe.** Since webpack@5 recommends [configuration cleanup](https://webpack.js.org/migrate/5/?_sm_au_=iVVn83n2sDMW0RFrMjpfkK68cqsfp#clean-up-configuration) and `output.path` removing... > Consider removing defaults: Using output.path: path.resolve(__dirname, 'dist'): you can omit it,...
This change helps for cases when `useCompilerPath` option is used, but `output.path` is not defined (since it is optional https://webpack.js.org/migrate/5/?_sm_au_=iVVn83n2sDMW0RFrMjpfkK68cqsfp#clean-up-configuration ) Closes: #403
**Describe the bug** `webpack-assets.json` gets removed if the new [output.clean](https://webpack.js.org/guides/output-management/?_sm_au_=iVVn83n2sDMW0RFrMjpfkK68cqsfp#cleaning-up-the-dist-folder) webpack@5 option is used. **To Reproduce** Steps to reproduce the behavior: ``` npm init -y npm i webpack assets-webpack-plugin webpack-cli...
**Describe the bug** Because Webpack will use way too much memory when it's left watching files during a whole workday if the output files include a hash in their name,...
**Describe the bug** We use webpack to generate multiple outputs and it works with 6.0 but with 6.1 it only outputs the second group of values and not both the...
**Describe the bug** If the code changes in a significant way (running `yarn install` is the easiest way to reproduce this) and a new chunk is generated, then the output...
I think it would be useful for the processOutput callback to have access to the compilation stats as a second parameter. In my case, I need the output asset map...