Skip to content
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: resolve #388

Closed
bitpshr opened this issue Apr 9, 2018 · 2 comments · Fixed by #405
Closed

Update transformation: resolve #388

bitpshr opened this issue Apr 9, 2018 · 2 comments · Fixed by #405
Labels

Comments

@bitpshr
Copy link
Member

bitpshr commented Apr 9, 2018

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 to v2.

What is the expected behavior?
The transformation should support migrating a webpack configuration from v3 to v4.

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 as v1 or v2 will no longer be supported.

This feature request is to update the resolve transformation accordingly.

@evenstensberg evenstensberg added this to the Vatican (v3) milestone Apr 10, 2018
@matheus1lva
Copy link
Member

This is for v2->v3, which is also present in here. Issue can be closed. Also, folder can be deleted (?)

@bitpshr
Copy link
Member Author

bitpshr commented Apr 15, 2018

PR submitted for the removal of this transformation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants