Skip to content
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

Merged
merged 1 commit into from Oct 28, 2020

Conversation

JLHwung
Copy link
Contributor

@JLHwung JLHwung commented Oct 27, 2020

Q                       A
Fixed Issues? export { foo } assert { type: "json" }; should be disallowed
Patch: Bug Fix? Y
License MIT

This PR fixes a bug we introduced in #12249, import assertions should only be parsed when we have seen from.

@JLHwung JLHwung added PR: Bug Fix 🐛 A type of pull request used for our changelog categories pkg: parser labels Oct 27, 2020
@babel-bot
Copy link
Collaborator

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/31228/

@codesandbox-ci
Copy link

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:

Sandbox Source
babel-repl-custom-plugin Configuration
babel-plugin-multi-config Configuration

@existentialism existentialism changed the title fix: disallow import assertionts in export without from fix: disallow import assertions in export without from Oct 27, 2020
]
],
"sourceType": "module",
"throws": "Unexpected token, expected \";\" (2:15)"
Copy link
Member

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)

Copy link
Contributor Author

@JLHwung JLHwung Oct 27, 2020

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.

Copy link
Member

@sosukesuzuki sosukesuzuki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@nicolo-ribaudo nicolo-ribaudo merged commit b7754d3 into babel:main Oct 28, 2020
@nicolo-ribaudo nicolo-ribaudo deleted the disallow-assertions-without-from branch October 28, 2020 06:07
sosukesuzuki added a commit to prettier/prettier that referenced this pull request Nov 6, 2020
@github-actions github-actions bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Jan 29, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue pkg: parser PR: Bug Fix 🐛 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants