Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
1.3-modules-beta.5 - Missing class properties transform. #6096
Class properties are only at stage 1 of standardization, which means the syntax and semantics could still change drastically: https://github.com/tc39/ecma262#current-proposals, https://github.com/jeffmo/es-class-fields-and-static-properties
If you really want to use this feature now, you should fork the
Coming back on this issue - the syntax did change dramatically! Boy, I'm glad I didn't write a lot of code with the old syntax.
It's in stage 2 now, and I got here by talking to someone who was trying to follow learnapollo.com in Meteor: https://forums.meteor.com/t/learnapollo-meteor-or-how-to-deal-with-the-es7-and-es6-issues/32558
It seems like a lot of React tutorials are now assuming this transform is on, so perhaps it's a good time to switch it on by default? It does depend on how likely it is for the syntax to change.
If it were Stage 3, I'd be more in favor of turning it on right now; it's hard to say how much it will change from Stage 2.
Timing-wise, I might suggest that we review all transforms at closer to 2017-02-01 as this might give ES2017 time to surface (TC39 meeting is sometime in January). Also, UglifyJS is rumored to get harmony support around then. I link these two things together only because there might be some similar considerations.
Im having this issue with mobx & Meteor 1.4.4.x
exampleStore.js: Missing class properties transform.
exampleStore.js works fine when written like this:
I do have .babelrc:
Other decorators work fine like action and computed.