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

Migrate functionality doesn't work as expected #1422

Closed
jamesgeorge007 opened this issue Apr 5, 2020 · 1 comment · Fixed by #1495
Closed

Migrate functionality doesn't work as expected #1422

jamesgeorge007 opened this issue Apr 5, 2020 · 1 comment · Fixed by #1495
Assignees
Labels

Comments

@jamesgeorge007
Copy link
Member

Describe the bug

What is the current behavior?
The migrate command doesn't work as expected, it throws an error without updating the config file.

To Reproduce

Type in webpack-cli migrate <path-to-config>

Expected behavior
The config is updated as expected.

Screenshots
Screenshot 2020-04-06 at 12 27 56 AM

Please paste the results of webpack-cli info here, and mention other relevant information

  System:
    OS: macOS 10.15.4
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
    Memory: 624.41 MB / 8.00 GB
  Binaries:
    Node: 13.11.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
  Browsers:
    Safari: 13.1
  npmPackages:
    webpack: ^1.15.0 => 1.15.0 
  npmGlobalPackages:
    webpack-cli: 4.0.0-beta.8

Additional context
N/A

@jamesgeorge007
Copy link
Member Author

Done in #1495

@jamesgeorge007 jamesgeorge007 linked a pull request Apr 27, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant