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
fix: disallow import assertions in export without from #12264
fix: disallow import assertions in export without from #12264
Conversation
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/31228/ |
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 c877a7a:
|
] | ||
], | ||
"sourceType": "module", | ||
"throws": "Unexpected token, expected \";\" (2:15)" |
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.
Wonder if we should point out a missing from
in the error message given assertions
? (Might be better DX)
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.
I think it is okay here because when from
is missing
export { someExport } asserts { type: "json" }
it would first throw
"someExport" is not defined
If users have already provided someExport
, it is unlikely someExport
could be exported from another module and thus they should consider remove the assertions.
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.
Thanks!
export { foo } assert { type: "json" };
should be disallowedThis PR fixes a bug we introduced in #12249, import assertions should only be parsed when we have seen
from
.