chore(deps): update dependency react-router-dom to v7.18.5 by renovate[bot] · Pull Request #1040 · block/builderbot

renovate · 2026-11-09T00:38:42Z

This PR contains the following updates:

Package	Change	Age	Confidence
react-router-dom (source)	`7.14.1` → `7.18.5`

Release Notes

remix-run/react-router (react-router-dom)

Date: 2026-06-16

What's Changed

CSRF Check Logic Fix

We made a bug fix in our underlying CSRF checks in this release that may be a "breaking bug fix" for some users deployed behind a reverse proxy. The CSRF check now checks directly against the host in the request url provided, instead of looking directly at HTTP headers which is an adapter concern. If your adapter is not setting the expected host in the request URL, you may need to add the new internal host to your allowedActionOrigins config. This is most likely to occur in @react-router/serve apps or @react-router/express apps without the trust proxy setting enabled. We recommend testing this against application mutation requests as part of your upgrade.

Minor Changes

@react-router/architect - Add a useRequestContextDomainName option to createRequestHandler to derive request URL hosts from the API Gateway request context (#15185)
- This flag will become the default behavior in v8, so it is recommended to adopt to prepare for and to v8 better align with your deployment architecture and rely less on manual header parsing in the adapter
- See the docs for more information

Patch Changes

react-router - Fix server handler prerender responses when using ssr: false and future.v8_trailingSlashAwareDataRequests: true (#15173)
- Avoids false positive "SPA Mode" detection when serving prerendered paths
react-router - Use the ServerRouter nonce for nonce-aware SSR components when they don't provide their own value so strict CSP pages can load them (#15170)
react-router - Use turbo-stream to serialize and deserialize Framework Mode hydration errors (#15175)
react-router - Optimize route matching by extending precomputed route branches to include matchers (#15186)
react-router - Use the constructed request URL host instead of header checks when validating action request origins in the CSRF check (#15185)
react-router - Remove the un-documented custom error serialization logic from Data Mode SSR built-in hydration flows (#15175)
react-router - Validate protocols in RSC render redirects (#15177)
react-router - Consolidate url normalization logic and better handle mixed slashes (#15176)
@react-router/dev - Pass Vite server.watch config to child compiler in development mode. (#15178)
@react-router/dev - Ignore external Vite server environments in Framework Mode build hooks (#14883)
- When future.v8_viteEnvironmentApi is enabled, React Router previously treated any non-client Vite environment as its own server build
- This caused issues with integrations like Nitro, where plugins can register additional environments
- Framework Mode build hooks now ignore external server environments and only process the app's own server build
@react-router/express - Adjust express adapter host computation (#15185)
- read port from x-forwarded-host based on trust proxy setting
- handle invalid hostname characters

Full Changelog: v7.17.0...v7.18.0

`v7.17.0`

Compare Source

Date: 2026-06-04

Minor Changes

react-router - Ship a subset of the official documentation inside the react-router package (#15121)
- Markdown docs are now available in node_modules/react-router/docs, letting AI coding agents and the React Router agent skills read official docs locally
- Excludes auto-generated API docs (api/), community/ content, and tutorials (tutorials/)

Patch Changes

@react-router/dev - Fix future flag warning URLs and only log each future flag warning one time (#15138)

Unstable Changes

⚠️ Unstable features are not recommended for production use

@react-router/dev - Prevent RSC route module server exports from being scanned by the client dependency optimizer when future.unstable_optimizeDeps is enabled. (#15005)

Full Changelog: v7.16.0...v7.17.0

`v7.16.0`

Compare Source

Date: 2026-05-28

Minor Changes

react-router - Stabilize future.unstable_trailingSlashAwareDataRequests as future.v8_trailingSlashAwareDataRequests (#15098)
@react-router/dev - Stabilize future.unstable_trailingSlashAwareDataRequests as future.v8_trailingSlashAwareDataRequests (#15098)
- The unstable flag is no longer supported and will error during config resolution
@react-router/dev - Log future flag warnings for upcoming React Router v8 flags (#15029)
- v8_middleware, v8_splitRouteModules, v8_viteEnvironmentApi, v8_passThroughRequests, v8_trailingSlashAwareDataRequests

Patch Changes

react-router - Disable manifest path when lazy route dicovery is disabled (#15068)
react-router - Fix browser URL creation to use the configured history window instead of the global window. (#15066)
- Pass the history/router window through to createBrowserURLImpl so custom window contexts keep the correct URL origin.
react-router - Fix useNavigation() return type to preserve discriminated union across navigation states (#15095)
react-router - Widen MetaDescriptor script:ld+json type from LdJsonObject to LdJsonObject | LdJsonObject[] to permit multiple JSON-LD schemas in a single <script type="application/ld+json"> tag emitted by <Meta /> (#15082)
react-router-dom - Remove stale/invalid unpkg field from package.json. This was removed from other packages with the release of v7 but missed in the react-router-dom re-export package (#15075)
@react-router/express - Ignore writes after Express responses close (#15107)
- Avoid surfacing client disconnects as adapter errors when the response stream has already been destroyed or ended.
@react-router/node - Honor Node writable backpressure in writeReadableStreamToWritable and writeAsyncIterableToWritable (#15071)
- Await 'drain' when writable.write() returns false instead of letting chunks accumulate in the writable's internal buffer.
- Reject (rather than hang) if the writable errors or closes mid-stream.
@react-router/serve - Normalize assetsBuildDirectory path separators in react-router-serve so Windows-built server artifacts can serve /assets/* correctly when run on Linux. (#14982)

Full Changelog: v7.15.1...v7.16.0

`v7.15.1`

Compare Source

Date: 2026-05-14

What's New

`useRouterState` (unstable)

Following our Less is More design goal, this release includes a new unstable_useRouterState() hook (Framework + Data Mode) that consolidates access to active and pending router states (RFC, Roadmap Issue).

This should allow you to consolidate usages of a bunch of different hooks which will likely be marked deprecated later on in v8 and potentially removed in an eventual v9:

let { active, pending } = unstable_useRouterState();

// Active is always populated with the current location
active.location; // replaces `useLocation()`
active.searchParams; // replaces `useSearchParams()[0]`
active.params; // replaces `useParams()`
active.matches; // replaces `useMatches()`
active.type; // replaces `useNavigationType()`

// Pending is only populated during a navigation
pending.location; // replaces `useNavigation().location`
pending.searchParams; // equivalent to `new URLSearchParams(useNavigation().search)`
pending.params; // Not directly accessible today
pending.matches; // Not directly accessible today
pending.type; // Not directly accessible today
pending.state; // replaces `useNavigation().state`
pending.formMethod; // replaces useNavigation().formMethod
pending.formAction; // replaces useNavigation().formAction
pending.formEncType; // replaces useNavigation().formEncType
pending.formData; // replaces useNavigation().formData
pending.json; // replaces useNavigation().json
pending.text; // replaces useNavigation().text

Patch Changes

react-router - Memoize useFetchers to return a stable identity and only change if fetchers changed (#15028)
react-router - Update router to operate on fetcher Maps in an immutable manner to avoid delayed React renders from potentially reading an updated but not yet committed Map. This could result in brief flickers in some fetcher-driven optimistic UI scenarios (#15028)
react-router - Fix serverLoader() returning stale SSR data when a client navigation aborts pending hydration before the hydration clientLoader resolves (#15022)
react-router - Fix RouterProvider onError callback not being called for synchronous initial loader errors in SPA mode (#15039) (#14942)
react-router - Internal refactor to consolidate mutation request detection through shared utility (#15033)
@react-router/dev - Fix basename conflicting with app directory name when Vite base is set (#15027)
- When the Vite base config and React Router basename both match the app directory name (e.g. base: "/app/", basename: "/app/"), Vite would strip the base prefix from server-build virtual module import paths, causing "Failed to load url /root.tsx" errors
- The fix uses /@fs/ absolute paths for those imports to bypass Vite's base-stripping logic

Unstable Changes

⚠️ Unstable features are not recommended for production use

react-router - Add a new unstable_useRouterState() hook that consolidates access to active and pending router states (RFC: #12358) (#15017)
- Data/Framework/RSC only — throws when used without a data router

Full Changelog: v7.15.0...v7.15.1

`v7.15.0`

Compare Source

Date: 2026-05-05

What's Changed

Stabilizations

We've stabilized a bunch of APIs in this release in preparation for a React Router v8 release hopefully in the next month or two. These flag/prop renames are breaking changes if you've already opted into the unstable APIs so please make sure you make the appropriate changes if so.

future.unstable_passThroughRequests → future.v8_passThroughRequests
future.unstable_subResourceIntegrity → top-level config.subResourceIntegrity
prerender.unstable_concurrency → prerender.concurrency
unstable_url → url (loader, action, middleware, instrumentation args)
unstable_instrumentations → instrumentations
- Plus associated types (ServerInstrumentation, ClientInstrumentation, etc.)
unstable_pattern → pattern (loader, action, middleware, instrumentation args)
unstable_defaultShouldRevalidate → defaultShouldRevalidate
unstable_useTransitions → useTransitions
unstable_mask → mask (on <Link>, useLinkClickHandler, useNavigate, and Location)

Route matching optimizations

We've added a handful of route matching optimizations in this release for Framework and Data mode. The changes are mostly related to caching the internal flattened/ranked route branches and reducing additional calls to matchRoutes along the critical path. This should result in improved performance during both server-side request handling and client-side navigations.

Minor Changes

react-router - Stabilize unstable_defaultShouldRevalidate as defaultShouldRevalidate on <Link>, <Form>, useLinkClickHandler, useSubmit, fetcher.submit, and setSearchParams (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
react-router - Stabilize the instrumentation APIs (14999)
- unstable_instrumentations is now instrumentations
- unstable_pattern is now pattern
- The unstable_ServerInstrumentation, unstable_ClientInstrumentation, unstable_InstrumentRequestHandlerFunction, unstable_InstrumentRouterFunction, unstable_InstrumentRouteFunction, and unstable_InstrumentationHandlerResult types have had their unstable_ prefixes removed
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
react-router - Stabilize unstable_mask as mask on <Link>, useLinkClickHandler, and useNavigate, and rename the corresponding Location.unstable_mask field to Location.mask (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
react-router - Stabilize the unstable_normalizePath option on staticHandler.query and staticHandler.queryRoute as normalizePath (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
react-router - Stabilize future.unstable_passThroughRequests as future.v8_passThroughRequests (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
react-router - Remove unstable_subResourceIntegrity from the runtime FutureConfig type; the flag is now controlled by the top-level subResourceIntegrity option in react-router.config.ts (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
react-router - Stabilize unstable_url as url on loader, action, and middleware function args (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
react-router - Stabilize unstable_useTransitions as useTransitions on <BrowserRouter>, <HashRouter>, <HistoryRouter>, <MemoryRouter>, <Router>, <RouterProvider>, <HydratedRouter>, and useLinkClickHandler (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
@react-router/dev - Stabilize future.unstable_passThroughRequests as future.v8_passThroughRequests (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
@react-router/dev - Stabilize prerender.unstable_concurrency as prerender.concurrency (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
@react-router/dev - Stabilize future.unstable_subResourceIntegrity as a top-level subResourceIntegrity config option in react-router.config.ts (14999)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

Patch Changes

react-router - Add nonce to <Scripts> <link rel="modulepreload"> elements (if provided) (af5d49b)
react-router - Fix a bug with unstable_defaultShouldRevalidate={false} where parent routes that did not export a shouldRevalidate function could be incorrectly included in the single fetch call for new child route data (#15012)
react-router - Mark mask as an optional field in Location for easier mocking in unit tests (#14999)
react-router - Improve server-side route matching performance by pre-computing flattened/cached route branches (#14967)
- Performance benchmarks showed roughly a 10-15% improvement in server-side request handling performance
react-router - Cache flattened/ranked route branches to optimize server-side route matching (#14967)
react-router - Improve route matching performance in Framework/Data Mode (#14971)
- Avoiding unnecessary calls to matchRoutes in data router scenarios
  - This includes adding back the optimization that was removed in 7.6.0 (#13562)
  - The issues that prompted the revert have been addressed by using the available router matches but always updating match.route to the latest route in the manifest
- Leverage pre-computed pre-computing flattened/cached route branches during client side route matching
- Performance benchmarks showed roughly a 15-30% improvement in server-side request handling performance

Full Changelog: v7.14.2...v7.15.0

`v7.14.2`

Compare Source

Date: 2026-04-21

Patch Changes

react-router - Remove the un-documented custom error serialization logic from the internal turbo-stream implementation. React Router only automatically handles serialization of Error and it's standard subtypes (SyntaxError, TypeError, etc.). (#14992)
react-router - Properly handle parent middleware redirects during fetcher.load (#14974)
react-router - Remove redundant Omit<RouterProviderProps, "flushSync"> from react-router/dom RouterProvider (#14874)

react-router - Improved types for generatePath's param arg (#14984)

Type errors when required params are omitted:

// Before
// Passes type checks, but throws at runtime 💥
generatePath(":required", { required: null });

// After
generatePath(":required", { required: null });
//                          ^^^^^^^^ Type 'null' is not assignable to type 'string'.ts(2322)

Allow omission of optional params:

// Before
generatePath(":optional?", {});
//                         ^^ Property 'optional' is missing in type '{}' but required in type '{ optional: string | null | undefined; }'.ts(2741)

// After
generatePath(":optional?", {});

Allows extra keys:

// Before
generatePath(":a", { a: "1", b: "2" });
//                           ^ Object literal may only specify known properties, and 'b' does not exist in type '{ a: string; }'.ts(2353)

// After
generatePath(":a", { a: "1", b: "2" });

@react-router/dev - Fix typegen for layouts without pages (#14875)
- Previously, typegen could produce pages: ; in .react-router/types/+routes.ts when a route corresponded to 0 pages
- Now, pages: never; is correctly generated for those cases

Unstable Changes

⚠️ Unstable features are not recommended for production use

@react-router/dev - For unstable_reactRouterRSC Vite plugin consumers, require @vitejs/plugin-react in user Vite config, and more reliably split route modules (#14965)
- ⚠️ This is a breaking change if you have begun using the unstable_reactRouterRSC Vite plugin - please install @vitejs/plugin-react and add the react plugin to your Vite plugins array.

Full Changelog: v7.14.1...v7.14.2

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

chatgpt-codex-connector · 2026-11-09T00:38:54Z

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-09T00:40:18.775170Z	`5a7bab5`	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

renovate Bot requested review from baxen, matt2e and wesbillman as code owners November 9, 2026 00:38

renovate Bot force-pushed the renovate/react-router-monorepo branch 7 times, most recently from 884ebac to fc3e40a Compare November 9, 2026 09:10

chore(deps): update dependency react-router-dom to v7.18.5

d49911b

renovate Bot force-pushed the renovate/react-router-monorepo branch from fc3e40a to d49911b Compare November 9, 2026 13:02

renovate Bot merged commit a3e3243 into main Nov 9, 2026
11 checks passed

renovate Bot deleted the renovate/react-router-monorepo branch November 9, 2026 13:17

Navigation Menu

Repository navigation

chore(deps): update dependency react-router-dom to v7.18.5 - #1040

chore(deps): update dependency react-router-dom to v7.18.5#1040
renovate[bot] merged 1 commit into
mainfrom
renovate/react-router-monorepo

renovate Bot commented Nov 9, 2026

Uh oh!

chatgpt-codex-connector Bot commented Nov 9, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Nov 9, 2026

Release Notes

What's Changed

CSRF Check Logic Fix

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Unstable Changes

Minor Changes

Patch Changes

What's New

useRouterState (unstable)

Patch Changes

Unstable Changes

What's Changed

Stabilizations

Route matching optimizations

Minor Changes

Patch Changes

Patch Changes

Unstable Changes

Configuration

Uh oh!

chatgpt-codex-connector Bot commented Nov 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

`useRouterState` (unstable)

chatgpt-codex-connector Bot commented Nov 9, 2026 •

edited

Loading