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

[Proposal] Remove ES2015 preset when Node 6 active LTS #275

Closed
2 tasks
jhen0409 opened this issue Jul 11, 2016 · 6 comments
Closed
2 tasks

[Proposal] Remove ES2015 preset when Node 6 active LTS #275

jhen0409 opened this issue Jul 11, 2016 · 6 comments

Comments

@jhen0409
Copy link
Member

Node 6 will active LTS in Oct 2016 (see this), and currently Electron is used Node 6 as runtime, we can only keep transform-es2015-modules-commonjs plugin. (It's not required in the Webpack 2)

Also, the problems:

@amilajack
Copy link
Member

We should use https://github.com/babel/babel-preset-env

@jhen0409
Copy link
Member Author

Yeah I think we should pointing to babel-preset-env and babili, and require node ^6 here, waiting for babel/babel#4755 merged, I'll do this.

@amilajack
Copy link
Member

amilajack commented Oct 25, 2016

Apparently its in beta. For the most part, I think it should be stable enough. What about you?

@hzoo
Copy link

hzoo commented Oct 25, 2016

You can always check the actual transforms with debug and then check that against the compat-table

@amilajack
Copy link
Member

@hzoo which compat table? Also do you think babli is stable enough to be used in production?

@hzoo
Copy link

hzoo commented Oct 28, 2016

https://github.com/kangax/compat-table is where the env data comes from - babili is still in beta but the more people testing it out the better so we can fix the bugs to make it more stable

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

No branches or pull requests

3 participants