Upgrade deps in non-package workspaces #2418
Merged
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
r100-stack
force-pushed
the
r/upgrade-deps
branch
from
87627ea to
ab88842
Compare
r100-stack
requested review from
mayank99 and
smmr-dn
and removed request for
a team and
smmr-dn
mayank99
reviewed
Feb 6, 2025
mayank99
approved these changes
Feb 6, 2025
This was referenced Feb 6, 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.
Changes
PR 1 in PR chain for #2387 (React 19 support). (PR 1: this PR, PR 2: #2424, PR 3: #2387).
Upgraded a couple of deps in non-package workspaces to help with React 19 support since some packages' older versions might not support React 19. Thus, to be safe, this helper PR upgrades some deps that may have fixed some problems in #2387 during its development.
Even this PR doesn't help a lot in the React 19 support, it wouldn't hurt to upgrade the deps to avoid potential issues. This is especially true since these upgrades are in non-package workspaces and so don't affect the user.
Testing
Docs
N/A since all the upgrades are in non-package workspaces and thus won't affect the user.