Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

babel presets: "es2015" deprecated, using "env" is recommended?

See original GitHub issue

from the babel docs: https://babeljs.io/docs/plugins/preset-es2015/

I had a compile error as I was using env instead, should I have the “es2015” preset for this library?

Issue Analytics

State:
Created 6 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

m4v15commented, Feb 15, 2018

@balestrinc I deleted “es2015” from their presets and added “stage-3” to my own (along with env) and it works fine. (apparently “env” doesn’t support stage-x plugins: https://github.com/babel/babel-preset-env/issues/14)

0reactions

robmadolecommented, May 2, 2018

We’ve switched to babel-env in the development branch.

Top Results From Across the Web

babel-preset-es2015 -> babel-preset-env - Babel.js

We're super excited that you're trying to use ES2015 syntax, but instead of continuing yearly presets, the team recommends using babel-preset-env.

2 - Stack Overflow

npm WARN deprecated babel-preset-es2015@6.24.1: Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env ...

babel-preset-es2015 - npm

This package has been deprecated Author message: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs ...

babel-preset-es2015 | Yarn - Package Manager

Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update! Babel preset for all es2015 plugins. readme ...

Search - appsloveworld

[Solved]-Npm WARN deprecated babel-preset-es2015@6.24.1: Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to ...