-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Add assertions
to ExportNamedDeclaration
without from
#13957
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/49785/ |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 6cd651e:
|
Co-authored-by: Nicolò Ribaudo <nicolo.ribaudo@gmail.com>
Ok, it looks like it doesn't support it 😬 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can assign assertions immediately after we have parsed them:
if (expect) { |
if (expect) { | ||
this.unexpected(); | ||
} else { | ||
node.source = null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, node.source = null
is called in maybeParseExportNamedSpecifiers
and maybeParseExportDeclaration
. So we can remove this from here.
Add
assertions
toExportNamedDeclaration
withoutfrom
whenimportAssertions
is enabled.According to estree spec: