fix: resolve punycode deprecation warning from jest-environment-jsdom #1893
Conversation
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
bchew
force-pushed
the
jest-jsdom-punycode
branch
from
c83653a to
a638113
Compare
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1893 +/- ##
=======================================
Coverage 99.73% 99.73%
=======================================
Files 94 94
Lines 1868 1868
Branches 552 552
=======================================
Hits 1863 1863
Misses 5 5 ☔ View full report in Codecov by Sentry. |
romi-h
approved these changes
Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Resolve punycode deprecation warning from jest-environment-jsdom
Does this PR introduce a breaking change?
Manual testing step?
Screenshots (if appropriate):