-
Notifications
You must be signed in to change notification settings - Fork 4
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 ExperimentalWarning
about importAssertions
#12
Merged
laverdet
merged 3 commits into
braidnetworks:main
from
danielfinke:use-importAttributes-instead-of-importAssertions
Feb 11, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
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.
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.
Good catch on the unused expression above.
I don't think this is what we want though. I believe this would prevent legacy
asserts
syntax from working after nodejs v18.20. v18 & v20 are supposed to be the transitional versions where either syntax works. So it gives teams a chance to migrate.I think there need to be two distinct regular expressions. The first is the most aggressive/eager, in order to avoid deprecation warnings. That's the one you authored in
loader.ts
, it looks correct to me. The second one would be the least aggressive option, which should go here. I think it would be/^(?:16|17|18|19|20|21)/
. So even if the user is usingasserts
syntax in nodejs v20 we will still allow it. It will hide the deprecation notice from them which is unfortunate but definitely not worth making our own deprecation notice.