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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch from preset-latest to preset-env #1711

Closed
Timer opened this Issue Mar 3, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@Timer
Collaborator

Timer commented Mar 3, 2017

We should probably switch babel-preset-react-app from babel-preset-latest to babel-preset-env. We should target ie 9.

We now have this beautiful warning:

warning react-scripts > babel-preset-react-app > babel-preset-latest@6.22.0:
馃挜  preset-latest accomplishes the same task as babel-preset-env.
馃檹  Please install it with 'npm install babel-preset-env --save-dev'.
'{ "presets": ["latest" }'
 to 
'{ "presets": ["env"] }'.

For more info, please check the docs: http://babeljs.io/docs/plugins/preset-env 馃憣.
And let us know how you're liking Babel at @babeljs on 馃惁

A PR doing this would be welcome, but please research the stability, too!

@Timer Timer changed the title from Switch to preset-env? to Switch from preset-latest to preset-env Mar 3, 2017

@Timer Timer added this to the 0.10.0 milestone Mar 4, 2017

Timer added a commit to Timer/create-react-app that referenced this issue Mar 6, 2017

Switch to preset-env
Disables modules to resolve facebook#1711
@Timer

This comment has been minimized.

Collaborator

Timer commented Mar 6, 2017

@Timer Timer closed this Mar 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment