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

fix: Install correct (es2015) babel preset to match generated config #138

Merged
merged 1 commit into from
May 13, 2017
Merged

Conversation

nilliams
Copy link
Contributor

What kind of change does this PR introduce?
Bugfix

Did you add tests for your changes?
No (none in repo)

If relevant, did you update the documentation?
N/A

Summary
Raised in #135, but I didn't address this outstanding problem in the previous PR.

The config generated uses presets: ['es2015'], see: https://github.com/webpack/webpack-cli/blob/master/lib/creator/yeoman/utils/module.js#L8

... but are previously installing babel-preset-env instead, which results in: Error: Couldn't find preset "es2015" when user answers 'y' to 'Will you be using ES2015?', then runs webpack.

Does this PR introduce a breaking change?
No

The config generated uses `presets: ['es2015']`, see: https://github.com/webpack/webpack-cli/blob/master/lib/creator/yeoman/utils/module.js#L8

... but are previously installing `babel-preset-env` instead, which causes error when user answers `y` to 'Will you be using ES2015?', then runs `webpack`.
@evenstensberg evenstensberg self-requested a review May 13, 2017 11:55
Copy link
Member

@evenstensberg evenstensberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why didn't you include this in the previous PR? Lgtm.

@evenstensberg evenstensberg merged commit b0af53f into webpack:master May 13, 2017
@nilliams
Copy link
Contributor Author

Thanks! Sorry I did mention that this was outstanding in the last comment in that issue. I wasn't sure what the intended babel preset was at the time, but it became clear this is the only fix that made sense after a bit of reading into babel-preset-env, and sleep 😀

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

Successfully merging this pull request may close these issues.

2 participants