chore(deps): update uuid to v9 #4397
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
|
❤️ |
yoyoonarock
force-pushed
the
bump-uuid-v9
branch
from
a3f0097 to
972f6f0
Compare
|
any word on this? |
|
this would be awesome 🙏 we have a few workarounds because of |
yoyoonarock
changed the title
yoyoonarock
force-pushed
the
bump-uuid-v9
branch
from
972f6f0 to
4ef0407
Compare
trivikr
approved these changes
Feb 14, 2024
2 tasks
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 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.
Issue
#3964
Description
uuidto v9.0.1@types/uuidto v9.0.4Testing
Wasn't able to test this locally cause my computer is super slow, hoping PR checks will run tests for me
Additional context
uuidv9.0.0 removes the need for a workaround for amoduleNameMapperor custom resolver when mocking in Jest.Related PR: microsoft/accessibility-insights-web#5421 (comment)
First time contributing, so happy to take feedback or help out however I can
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.