Skip to content

Update dependency remix-run/react-router to v7.14.0#554

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/react-router-monorepo
Open

Update dependency remix-run/react-router to v7.14.0#554
renovate[bot] wants to merge 1 commit intomainfrom
renovate/react-router-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 6, 2026

This PR contains the following updates:

Package Update Change
remix-run/react-router minor 7.13.27.14.0

Release Notes

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

v7.14.0

Compare Source

Date: 2026-04-02

Minor Changes
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: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants