React Router v8 upgrade POC (AI-assisted)#12191
Draft
slorber wants to merge 1 commit into
Draft
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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
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.
Pre-flight checklist
Motivation
POC upgrade of Docusaurus from React Router v5 to React Router v8, with
history@5.This intentionally focuses on proving that the current Docusaurus website can build with the latest React Router stack. It does not attempt to complete the full migration, update all tests, or fully polish public types yet.
This PR was prepared with AI assistance. (AI-assisted)
What changed:
react-router@8.0.1.historyto5.3.0.19.2.7, matching React Router v8 requirements.react-router-domandreact-router-configfrom the runtime path.@docusaurus/routerconsumers can still access auseHistory-style API during the POC.Important caveats:
PendingNavigationwas simplified because the previous React Router v5 controlled<Route location>pattern does not map cleanly to v8.minimumReleaseAgesetting because React Router v8 is very recent.Test Plan
Validated locally:
Test links
Deploy preview: https://deploy-preview-12191--docusaurus-2.netlify.app/