Skip to content
This repository has been archived by the owner on Jun 29, 2018. It is now read-only.

Set defaualt presets as latest,stage-0,react #52

Open
murashki opened this issue Aug 28, 2016 · 4 comments
Open

Set defaualt presets as latest,stage-0,react #52

murashki opened this issue Aug 28, 2016 · 4 comments

Comments

@murashki
Copy link

murashki commented Aug 28, 2016

Perhaps it would be advisable to set defaualt presets as latest,stage-0,react (or latest,stage-1,react). We have es2015,react default presets, but why? Why not es2015,es2016 (current year) or latest?

I propose to fix default presets, or we must provide understandable explanation (logic, strategy) of which presets currently default and why.

Thanks for your work!

@Daniel15
Copy link
Member

Maybe es2016 should be included as default, but stage 0 proposals are generally not stable enough to be recommended for wide use (eg. as a default). ECMAScript proposals that are at stage 0 can be rejected or totally removed from the spec, and you use them at your own risk 😄

@murashki
Copy link
Author

Your comment (recommendation) about stage-0 certainly useful when we decide use some features or not in out codebase. But this recommendation may be slightly inappropriate when we talk about transpiler defaults. I mean this are different things...

Ok. So i see such variants as:
latest,stage-0,react
latest,stage-1,react - good idea for transpiler defaults! :)
latest,stage-4,react
latest,react

@hzoo
Copy link
Member

hzoo commented Oct 1, 2016

latest as default sounds fine

@murashki
Copy link
Author

murashki commented Oct 1, 2016

But React Start App use stage-0 by default, and I think this is right deсision!

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

No branches or pull requests

3 participants