-
-
Notifications
You must be signed in to change notification settings - Fork 54
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 packages appropriately for Webpack v1 compatibility #34
Conversation
Fixing test failure that's happening because my code assumes dev deps always exist. |
cf4da9b
to
a3b6144
Compare
Great, we just need a test fixture for this as well |
a3b6144
to
0919fbe
Compare
0919fbe
to
885f96e
Compare
Updated! |
{ | ||
"name": "webpack-v1-compatibility", | ||
"devDependencies": { | ||
"babel-loader": "^7.1.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I was confused why it should be 7.1.1 but I guess there's an issue?
// Later versions of babel-loader are incompatible with Webpack v1. | ||
// https://github.com/babel/babel-loader/issues/505 | ||
if (depsWebpack1 && dependencies['babel-loader']) { | ||
console.log('Updating babel-loader to v7.1.1 as this project uses Webpack v1'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should say, please update webpack if you can 😄 https://webpack.js.org/guides/migrating/? don't have to
Fixes #17.
When
babel-upgrade
is run over a project that uses Webpack v1:[email protected]
(from this suggestion)babel-core@^7.0.0-bridge.0
This repo repros the bug from this issue. Running
babel-upgrade --install
with the diff from this PR fixes the Webpack error.