Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.7k
Fix: always initialize ExportDeclaration attributes#17164
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
Collaborator
babel-bot commentedMar 6, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Build successful! You can test your changes in the REPL here:https://babeljs.io/repl/build/58815 |
nicolo-ribaudo approved these changesMar 6, 2025
74f5d6d
intobabel:main 55 checks passed
Uh oh!
There was an error while loading.Please reload this page.
laine-hallot pushed a commit to laine-hallot/uwu-parser that referenced this pull requestMar 31, 2025
* chore: bump eslint and espree* fix: always initialize ExportDeclaration attributes* update AST fixtures* fix: initialize attributes when importAssertions is not enabled* update AST fixtures* update test snapshot* update Makefile.js* update Babel 8 AST fixtures
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Labels
outdatedA closed issue/PR that is archived due to age. Recommended to make a new issue PR: Bug Fix 🐛A type of pull request used for our changelog categories PR: Fixes failing main
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.
Uh oh!
There was an error while loading.Please reload this page.
The CI is failing because recently espree supported the ES2025 import attributes. espree always initialize
attributes
for the export declaration while Babel only do so when we see thefrom ...
source.I think this is a bug for us since we already handle it in the espree's way for the legacy import assertions, but somehow it is overlooked in import attributes. Here we will initialize
attributes
property unlessimportAssertions
plugin is enabled.