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

Repurpose `babel` npm package #4951

Closed
hzoo opened this Issue Dec 7, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@hzoo
Member

hzoo commented Dec 7, 2016

Update the babel npm package to do something again: Make it the default/opt-in/opinionated babel that Babel 5 was. It can default to using env and say the latest 2 browsers (without any config).

to combat the fatigue. We could even figure out how to do an "eject" feature that turns it into babel-cli + a .babelrc

@hzoo hzoo added the i: discussion label Dec 7, 2016

@hzoo

This comment has been minimized.

Show comment
Hide comment
@hzoo

hzoo Feb 15, 2017

Member

If/when we switch to @babel we can't use this. So if anything maybe create a babel-cli-env? Although you'd probably use babel-loader for browser code. For node maybe we just need to make babel-node/babel-register prod ready

Member

hzoo commented Feb 15, 2017

If/when we switch to @babel we can't use this. So if anything maybe create a babel-cli-env? Although you'd probably use babel-loader for browser code. For node maybe we just need to make babel-node/babel-register prod ready

@hzoo

This comment has been minimized.

Show comment
Hide comment
@hzoo

hzoo Mar 19, 2017

Member

We can decide what to do without this issue 😄

Member

hzoo commented Mar 19, 2017

We can decide what to do without this issue 😄

@hzoo hzoo closed this Mar 19, 2017

@lock lock bot added the outdated label May 5, 2018

@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2018

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