Update dependency remix-run/react-router to v7.14.2

[renovate]

This PR contains the following updates:

Package	Update	Change
remix-run/react-router	minor	7.13.2 → 7.14.2

---

Release Notes

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

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

v7.14.1

Compare Source

Date: 2026-04-13

Patch Changes

• react-router - Fix a potential race condition that can occur when rendering a HydrateFallback and initial loaders land before the router.subscribe call happens in the RouterProvider layout effect (#​14497)
• react-router - Normalize double-slashes in redirect paths (#​14962)
• @react-router/dev - Add TypeScript 6 support to peer dependency ranges (#​14935)

Full Changelog: v7.14.0...v7.14.1

v7.14.0

Compare Source

Date: 2026-04-02

Minor Changes

• Add support for Vite 8 (#​14876)

Patch Changes

• react-router - Remove recursion from vendored turbo-stream v2 implementation allowing for encoding/decoding of large payloads (#​14838)
• react-router - Fix encodeViaTurboStream memory leak via unremoved AbortSignal listener (#​14900)
• @react-router/dev - Support for prerendering multiple server bundles with v8_viteEnvironmentApi (#​14921)

Unstable Changes

⚠️ Unstable features are not recommended for production use

• @react-router/dev - Pre-rendering and SPA Mode support for RSC Framework Mode (#​14907)
• @react-router/dev - Update react-router reveal to support RSC Framework Mode for entry.client, entry.rsc, entry.ssr (#​14904)
• react-router - Support <Link prefetch> in RSC Framework Mode (#​14902)
• react-router - Add support for new route module exports in unstable RSC Framework Mode (#​14901)

  • ⚠️ This is a breaking change if you have already adopted RSC Framework Mode in it's unstable state - you will need to update your route modules to export the new annotations

  • The following route module components have their own mutually exclusive server component counterparts:

    Client Component export	Server Component export
    default	ServerComponent
    ErrorBoundary	ServerErrorBoundary
    Layout	ServerLayout
    HydrateFallback	ServerHydrateFallback

  • If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also implicitly server components

  • If you want to keep those as server components - rename them and prefix them with Server

  • If you were previously importing the implementations of those components from a client module, you can inline them

    // Before
    import { ErrorBoundary as ClientErrorBoundary } from "./client";
    
    export function ServerComponent() {
      // ...
    }
    
    export function ErrorBoundary() {
      return <ClientErrorBoundary />;
    }
    
    export function Layout() {
      // ...
    }
    
    export function HydrateFallback() {
      // ...
    }

    // After
    
    export function ServerComponent() {
      // ...
    }
    
    export function ErrorBoundary() {
      // previous implementation of ClientErrorBoundary, this is now a client component
    }
    
    export function ServerLayout() {
      // rename previous Layout export to ServerLayout to make it a server component
    }
    
    export function ServerHydrateFallback() {
      // rename previous HydrateFallback export to ServerHydrateFallback to make it a server component
    }

Full Changelog: v7.13.2...v7.14.0

---

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: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.