-
Notifications
You must be signed in to change notification settings - Fork 130
Switch to ES6 format? #52
Comments
I agree that this is something we want to do, but we need to keep in mind that there is a lot of fragmentation in terms of transpilation methods / preferences across this package's user base. Not everyone is using ES6 (or ES7), and some only use a subset of features. Options to deal with this include:
If anyone has thoughts on this, please do chime in. |
I see. That make sense. |
My initial thought was to fork and add to the js snippets folder es6 friendly snippets(react_component6.sublime-snippet with a trigger of rcc6) while leaving the current ones because I actually work in an organization that has just begun to move to es6 and the move will take quite some time. |
Note that "es6-friendliness" is a blurry concept rather than a binary one; Take a look at the many options in popular transformers such as https://babeljs.io/docs/usage/options/. |
A lot of new features in ES6 makes code simpler.
like
import
,export
...ex:
Define method in object from
to
The text was updated successfully, but these errors were encountered: