-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with speed-measure-webpack-plugin #1090
Comments
Any updates about this? Really want to track down why the build time of my project is taking 18 minutes (!) long :) |
I guess nobody is working on it. |
remove speed-measure-webpack-plugin |
I meet the same error and compiler failed and i remove speed-measure-webpack that can compiler success. It seems that two plugin has compatible problem. |
Maybe https://github.com/jantimon/cpuprofile-webpack-plugin can help you here? |
Didn't solve this problem? |
I'll close this for now as nobody seems to work on this issue and https://github.com/jantimon/cpuprofile-webpack-plugin can provide more accurate speed measurements. |
Expected behavior
I would like to be able to continue using speed-measure-webpack-plugin to monitor build timings with the latest beta version of html-webpack-plugin.
Current behavior
The changes to reuse a single child compiler (#967) are awesome but unfortunately introduce an incompatibility with the way that speed-measure-webpack-plugin works. speed-measure-webpack-plugin uses a Proxy to wrap the compiler object which results in multiple child compilers being created by html-webpack-plugin (one for the original compiler and another for the wrapped one). This causes the following error because the templates are only set on one of the child compilers.
Happy to help fix but not sure which plugin is really at fault here.
Environment
Config
Reproduction repo
The text was updated successfully, but these errors were encountered: