-
Notifications
You must be signed in to change notification settings - Fork 23
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
build: webpack - warning "PurifyPlugin is deprecated and will be removed in 0.7.0" #623
Comments
Apparently the PurifyPlugin is deprecated in Angular 6.1.x because Webpack 4 provides the same functionality as this plugin and its TS transformer. We need to check and see if they provide some guidelines on how to configure Webpack to achieve the same functionality of this plugin. |
The PurifyPlugin is finally removed in Angular 7 because it is no longer needed as with Webpack 4 and its built-in module concatenation plugin.. So it seems we could just remove the plugin from our webpack config since we are using Angular 6.1.x (no need to wait until we upgrade to Angular 7). |
…s options to improve performanc ISSUES CLOSED: #623
…s options to improve performance. ISSUES CLOSED: #623
…glifyJs options to improve performance. ISSUES CLOSED: #623
…lifyJs options to improve performance. ISSUES CLOSED: #623
I'm submitting a...
Current behavior
A warning is displayed when running the application with webpack on DEV:
WARNING in PurifyPlugin is deprecated and will be removed in 0.7.0
Such warning was introduced in this commit: angular/devkit@cb2703e
Expected behavior
No warnings during webpack builds.
Minimal reproduction of the problem with instructions
Run
npm start
in the showcase or the starter.What is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: