You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2018. It is now read-only.
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!
The text was updated successfully, but these errors were encountered:
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 😄
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
Perhaps it would be advisable to set defaualt presets as
latest,stage-0,react
(orlatest,stage-1,react
). We havees2015,react
default presets, but why? Why notes2015,es2016
(current year) orlatest
?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!
The text was updated successfully, but these errors were encountered: