Comments (3)
I am having the same problem while doing a Node upgrade to 16. As far as I can see the problem is that the plugin registers itself with the legacy
compiler.hooks.emit.tapAsync(plugin, emitPlugin);
and is run with the legacy plugins. The compression plugin uses the new
compiler.hooks.thisCompilation.tap(pluginName, compilation => {compilation.hooks.processAssets.tapPromise({ name: pluginName, stage: compiler.webpack.Compilation.PROCESS_ASSETS_STAGE_OPTIMIZE_TRANSFER, additionalAssets: true } ...
So the fix would probably be running the plugin in processAssets/PROCESS_ASSETS_STAGE_REPORT and adding a parameter to choose between new and legacy mode?
from assets-webpack-plugin.
Can confirm this problem, latest everything.
from assets-webpack-plugin.
Same here. The strange part is if the "delete original assets" option is set in the compression plugin, it works. It only lists either the original assets, or the zipped assets if the original assets are set to be deleted. But not both. So if you're ok with just having the zipped assets, this is a viable workaround.
This is probably the same issue (so I didn't want to start one,) but it also clashes with the brotli plugin (https://www.npmjs.com/package/brotli-webpack-plugin) and doesn't list anything that is generated by it.
Love this plugin though! Such great work!
from assets-webpack-plugin.
Related Issues (20)
- Unnecessary output caused by console.log() HOT 1
- Output not generated with new chunk HOT 3
- Add auxiliary assets HOT 4
- CopyPlugin for copy files with hash, give me an empty field for images in webpackstats.json HOT 3
- Changing webpack compiler hook from emit to afterEmit HOT 2
- Adding dynamically imported modules to assets.json
- Multiple outputs broken by 6.0.6 HOT 3
- Change Behaviour to Behavior HOT 1
- Specify Webpack >=5.0.0 as peer dependency HOT 1
- integrity configuration not working HOT 24
- Action Required: Fix Renovate Configuration
- Output always includes hash since 7.1 HOT 1
- useCompilerPath option should respect webpack@5 defaults
- `webpack-assets.json` gets removed if `output.clean` webpack option is enabled HOT 1
- Dependency Dashboard
- Possible Typo in createOutputWriter.js HOT 3
- Ability to configure processOutput to be executed on afterEmit
- missing part of file in vue-cli modern mode
- `integrity` feature doesn't work with ` [email protected]`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from assets-webpack-plugin.