Update react-router to v8.0.1#1121
Conversation
Major version bump (7.17.0 -> 8.0.1), kept separate from the routine dependency-update PR because it crosses a major version. react-router v8's breaking changes are all in framework/data mode and tooling: the `meta` `data`->`loaderData` rename, the always-on `v8_middleware` (flag + `MiddlewareEnabled` type removed), the `<Form>` `onSubmit` type override removal, and a Node >= 22.22.0 minimum. This app uses declarative mode (`<BrowserRouter>`/`<Routes>`/`<Route>`) with only stable hooks (useParams, useNavigate, useSearchParams, useLocation, useNavigationType, Link, Navigate), runs on Node 24, and is already on React 19.2.7 (v8's required peer), so none of them apply — no code changes were needed. SBOM regenerated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 45 minutes and 22 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Bumps
react-router7.17.0 → 8.0.1 (major). Kept separate from the routine dependency-update PR (#1120) because it crosses a major version, per request.Why no code changes were needed
react-router v8's breaking changes are confined to framework/data mode and tooling, none of which this app uses:
metaAPIs:data→loaderDatameta)future.v8_middlewareflag removed; middleware always onMiddlewareEnabled/UNSAFE_MiddlewareEnabledtype removed<Form>onSubmittype override removed<Form>not usedreact/react-dom≥ 19.2.7The app uses declarative mode —
<BrowserRouter>/<Routes>/<Route>with only stable hooks/components (useParams,useNavigate,useSearchParams,useLocation,useNavigationType,Link,Navigate). All 52 react-router imports come from the unifiedreact-routerpackage; the API surface is unchanged in v8.Verification
pnpm build✓tsc --noEmit✓ (no errors — would flag any changed API signatures)eslint src/✓ (0 errors)pnpm test✓ (26 pass)Runtime routing is additionally exercised by the Playwright e2e suite in CI.
Notes
develop. Independent of Update dependencies (client pnpm, server Gradle, Docker/CI) and resolve Dependabot alerts #1120 (the routine dep PR, which bumps react-router to 7.18.0); whichever merges first, the other resolves trivially to its target version.🤖 Generated with Claude Code