-
Notifications
You must be signed in to change notification settings - Fork 28k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bind operator: unexpected token #266
Comments
Actually we just picked up some plugins which we thought fundamental. It might be better to enable only |
My take on this policy is that "whatever v8 has" is the best idea for us. Moving forward Node.js and Chrome seem to be in sync as far as v8 goes pretty aggressively. Otherwise we run the big risk of making the Next community use a feature that's never going to land and consider it a standard. |
@rauchg I agree the policy, but the problem is maybe V8 doesn't support what we already do (class properties, object-rest-spread). I assumed V8 will support or has supported all ES2015 features eventually. |
It looks V8 basically doesn't implement proposals and still does't support some adopted features (es2017) ? |
Those two presets sound great. We need to document what we support on the On Fri, Nov 18, 2016 at 12:49 PM Naoyuki Kanezawa notifications@github.com
|
@rauchg the problem is those two presets don't include class-properties and object-rest-spread which we already support and are stage2-3 yet. |
@nkzawa @rauchg how about this: https://www.npmjs.com/package/babel-preset-react-app It got |
I think it does have |
@jonaswindey yep it does. I changed my comment. I got it confused with static class methods. |
If you want to do any tracking I suggest you try using https://github.com/babel/babel-preset-env/ which I've been working on (preset-latest is just es2015, 16, 17) |
You can add this through the custom babel feature https://github.com/zeit/next.js#customizing-babel-config |
Stats from current PRDefault Server ModeGeneral
Client Bundles (main, webpack, commons)
Client Bundles (main, webpack, commons) Modern
Client Pages
Client Pages Modern
Client Build Manifests
Rendered Page Sizes
Serverless ModeGeneral
Client Bundles (main, webpack, commons)
Client Bundles (main, webpack, commons) Modern
Client Pages
Client Pages Modern
Client Build Manifests
Serverless bundles
Commit: 3762e75 |
Getting
Module build failed: SyntaxError: Unexpected token
when using the bind operator:<Button onClick={::this.handleSubmit}>
Any reason this isn't configured in babel?
The text was updated successfully, but these errors were encountered: