-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
Update transformation: uglifyJsPlugin #389
Labels
Comments
i'm working on this! |
Thanks! |
Quick question, i could not find in the docs. If i want to customize how the minification should work (add parameters, etc), i should use |
@montogeek thanks, good to know where i can find things! now i can go straight there. |
This was referenced Apr 12, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
The current transformation supports migrating a webpack configuration from
v1
tov2
.What is the expected behavior?
The transformation should support migrating a webpack configuration from
v3
tov4
.If this is a feature request, what is motivation or use case for changing the behavior?
After some discussion the decision was made to update our migration transformations to actively support migrating only from the previous version to the current version, which currently means
v3 - v4
. Migrating older versions such asv1
orv2
will no longer be supported.This feature request is to update the
uglifyJsPlugin
transformation accordingly.The text was updated successfully, but these errors were encountered: