-
Notifications
You must be signed in to change notification settings - Fork 1
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
Bump react-router & react-router-dom to v7.1.1 #2314
Draft
asiia-trilitech
wants to merge
3
commits into
main
Choose a base branch
from
migrate-react-router-to-v7
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 7, 2025 13:33
a8ce695
to
7616340
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 7, 2025 22:51
9a6f998
to
dcf265b
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 7, 2025 22:57
dcf265b
to
09e7dc1
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 7, 2025 23:06
09e7dc1
to
c718b0e
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 8, 2025 01:42
c718b0e
to
bec4a5c
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 8, 2025 08:51
3decfa5
to
c36d64a
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 9, 2025 09:58
c36d64a
to
70ff281
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 9, 2025 10:33
70ff281
to
9faa803
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 9, 2025 10:39
9faa803
to
675dd21
Compare
asiia-trilitech
force-pushed
the
migrate-react-router-to-v7
branch
from
January 9, 2025 12:26
675dd21
to
764c4a0
Compare
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.
Proposed changes
Manual migration of
react-router
&react-router-dom
to the latest version (v7.1.1)react-router changelog
Migration is being done in the following steps
useNavigate()
now exposes a promise (previously returned undefined).<Routes>
usagesTypes of changes
Checklist