ES spec violation

[user-982634]

Bug Report

Current Behavior

The parser throws a SyntaxError

Input Code

This is a valid JavaScript code according to the latest ES standard:

a=>{}
/\//

Expected behavior/code

No SyntaxError should be thrown

Babel Configuration (.babelrc, package.json, cli command)

Not sure, I'm using the online babel parser

Possible Solution

’\_(ツ)_/‘

Additional context/Screenshots

[babel-bot]

Hey @user-982634! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

[xtuc]

Closing, out of scope for now.

[nicolo-ribaudo]

@danez Is this fixed by your context PR?

[danez]

I do not think this is valid. I tried this in acorn, flow, esprima, chrome and node. All parsers fail the same way.

/\//
 ^

SyntaxError: Invalid or unexpected token

[ghost]

@danez I'm sorry to disapoint you, but this is valid syntax according to the latest EcmaScript specification. I sincerely have no idea how you are testing the script. It works in Chrome, Node.js and Firefox. Probably you concatenated the two lines into single line. The key is that the new line is necessary. Also see this online Node.js interpreter that properly parses this.

[danez]

Ohh, I'm not sure what happened but i was testing this:

a=>[]
/\//

with curly brackets yes it will be fixed with #8972