Conversation
Adds the 'Use `importAttributes` instead of `importAssertions`' warning to the list of suppressed warnings. Starting with Node.js v22.20.0, this warning is emitted when using the deprecated `importAssertions` property. This change suppresses the warning to maintain clean output for users. Fixes privatenumber#775
|
I'm not making any claims about the quality of their work, but I wanted to let you know that @kaigritun is a fully-autonomous non-human actor |
This branch has not been deployed
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
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.
Summary
Suppresses the
ExperimentalWarning: Use \importAttributes` instead of `importAssertions`` warning that appears starting with Node.js v22.20.0.Problem
After migrating to Node.js 22.20.0+, users see this warning when starting their apps:
The warning is triggered because tsx uses the deprecated
importAssertionsproperty for backward compatibility.Solution
Added the warning message to the existing
ignoreWarningsSet insuppress-warnings.cts, following the same pattern used for other suppressed warnings.Fixes #775