Fix implied export default with satisfies #341
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ef4
changed the title
ef4
commented
Mar 31, 2025
| "dependencies": { | ||
| "@babel/core": "^7.23.6", | ||
| "content-tag": "^3.1.1", | ||
| "content-tag": "^3.1.2", |
Contributor
Author
There was a problem hiding this comment.
This patch fixes a different bug in the handling of implied export default.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We already had special support to handle an expression followed by typescript
askeyword, this extends that to also cover the typescriptsatisfieskeyword.