chore: Update version for release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

Releases

[email protected]

Major Changes

• Remove the original defer implementation in favor of using raw promises via single fetch and turbo-stream. This removes these exports from React Router: (#11744)

  • defer
  • AbortedDeferredError
  • type TypedDeferredData
  • UNSAFE_DeferredData
  • UNSAFE_DEFERRED_SYMBOL,
• • Collapse @remix-run/router into react-router (#11505)
  • Collapse react-router-dom into react-router
  • Collapse @remix-run/server-runtime into react-router
  • Collapse @remix-run/testing into react-router

• Remove single_fetch future flag. (#11522)

• Drop support for Node 16, React Router SSR now requires Node 18 or higher (#11391)

• Remove future.v7_startTransition flag (#11696)

• • Expose the underlying router promises from the following APIs for compsition in React 19 APIs: (#11521)
    • useNavigate()
    • useSubmit
    • useFetcher().load
    • useFetcher().submit
    • useRevalidator.revalidate

• Remove future.v7_normalizeFormMethod future flag (#11697)

• For Remix consumers migrating to React Router, the crypto global from the Web Crypto API is now required when using cookie and session APIs. This means that the following APIs are provided from react-router rather than platform-specific packages: (#11837)

  • createCookie
  • createCookieSessionStorage
  • createMemorySessionStorage
  • createSessionStorage

  For consumers running older versions of Node, the installGlobals function from @remix-run/node has been updated to define globalThis.crypto, using Node's require('node:crypto').webcrypto implementation.

  Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:

  • createCookieFactory
  • createSessionStorageFactory
  • createCookieSessionStorageFactory
  • createMemorySessionStorageFactory

• Imports/Exports cleanup (#11840)

  • Removed the following exports that were previously public API from @remix-run/router
    • types
      • AgnosticDataIndexRouteObject
      • AgnosticDataNonIndexRouteObject
      • AgnosticDataRouteMatch
      • AgnosticDataRouteObject
      • AgnosticIndexRouteObject
      • AgnosticNonIndexRouteObject
      • AgnosticRouteMatch
      • AgnosticRouteObject
      • TrackedPromise
      • unstable_AgnosticPatchRoutesOnMissFunction
      • Action -> exported as NavigationType via react-router
      • Router exported as DataRouter to differentiate from RR's <Router>
    • API
      • getToPathname (@private)
      • joinPaths (@private)
      • normalizePathname (@private)
      • resolveTo (@private)
      • stripBasename (@private)
      • createBrowserHistory -> in favor of createBrowserRouter
      • createHashHistory -> in favor of createHashRouter
      • createMemoryHistory -> in favor of createMemoryRouter
      • createRouter
      • createStaticHandler -> in favor of wrapper createStaticHandler in RR Dom
      • getStaticContextFromError
  • Removed the following exports that were previously public API from react-router
    • Hash
    • Pathname
    • Search

• update minimum node version to 18 (#11690)

• Remove future.v7_prependBasename from the ionternalized @remix-run/router package (#11726)

• Migrate Remix type generics to React Router (#12180)

  • These generics are provided for Remix v2 migration purposes
  • These generics and the APIs they exist on should be considered informally deprecated in favor of the new Route.* types
  • Anyone migrating from React Router v6 should probably not leverage these new generics and should migrate straight to the Route.* types
  • For React Router v6 users, these generics are new and should not impact your app, with one exception
    • useFetcher previously had an optional generic (used primarily by Remix v2) that expected the data type
    • This has been updated in v7 to expect the type of the function that generates the data (i.e., typeof loader/typeof action)
    • Therefore, you should update your usages:
      • ❌ useFetcher<LoaderData>()
      • ✅ useFetcher<typeof loader>()

• Remove future.v7_throwAbortReason from internalized @remix-run/router package (#11728)

• Add exports field to all packages (#11675)

• node package no longer re-exports from react-router (#11702)

• renamed RemixContext to FrameworkContext (#11705)

• updates the minimum React version to 18 (#11689)

• PrefetchPageDescriptor replaced by PageLinkDescriptor (#11960)

• • Consolidate types previously duplicated across @remix-run/router, @remix-run/server-runtime, and @remix-run/react now that they all live in react-router (#12177)
    • Examples: LoaderFunction, LoaderFunctionArgs, ActionFunction, ActionFunctionArgs, DataFunctionArgs, RouteManifest, LinksFunction, Route, EntryRoute
    • The RouteManifest type used by the "remix" code is now slightly stricter because it is using the former @remix-run/router RouteManifest
      • Record<string, Route> -> Record<string, Route | undefined>
    • Removed AppData type in favor of inlining unknown in the few locations it was used
    • Removed ServerRuntimeMeta* types in favor of the Meta* types they were duplicated from
• • Remove the future.v7_partialHydration flag (#11725)
    • This also removes the <RouterProvider fallbackElement> prop
      • To migrate, move the fallbackElement to a hydrateFallbackElement/HydrateFallback on your root route
    • Also worth nothing there is a related breaking changer with this future flag:
      • Without future.v7_partialHydration (when using fallbackElement), state.navigation was populated during the initial load
      • With future.v7_partialHydration, state.navigation remains in an "idle" state during the initial load

• Remove v7_relativeSplatPath future flag (#11695)

• Drop support for Node 18, update minimum Node vestion to 20 (#12171)

  • Remove installGlobals() as this should no longer be necessary

• Remove remaining future flags (#11820)

  • React Router v7_skipActionErrorRevalidation
  • Remix v3_fetcherPersist, v3_relativeSplatPath, v3_throwAbortReason

• rename createRemixStub to createRoutesStub (#11692)

• Remove @remix-run/router deprecated detectErrorBoundary option in favor of mapRouteProperties (#11751)

• Add react-router/dom subpath export to properly enable react-dom as an optional peerDependency (#11851)

  • This ensures that we don't blindly import ReactDOM from "react-dom" in <RouterProvider> in order to access ReactDOM.flushSync(), since that would break createMemoryRouter use cases in non-DOM environments
  • DOM environments should import from react-router/dom to get the proper component that makes ReactDOM.flushSync() available:
    • If you are using the Vite plugin, use this in your entry.client.tsx:
      • import { HydratedRouter } from 'react-router/dom'
    • If you are not using the Vite plugin and are manually calling createBrowserRouter/createHashRouter:
      • import { RouterProvider } from "react-router/dom"

• Remove future.v7_fetcherPersist flag (#11731)

• Update cookie dependency to ^1.0.1 - please see the release notes for any breaking changes (#12172)

Minor Changes

• • Add support for prerender config in the React Router vite plugin, to support existing SSG use-cases (#11539)
    • You can use the prerender config to pre-render your .html and .data files at build time and then serve them statically at runtime (either from a running server or a CDN)
    • prerender can either be an array of string paths, or a function (sync or async) that returns an array of strings so that you can dynamically generate the paths by talking to your CMS, etc.

  // react-router.config.ts
  import type { Config } from "@react-router/dev/config";
  
  export default {
    async prerender() {
      let slugs = await fakeGetSlugsFromCms();
      // Prerender these paths into `.html` files at build time, and `.data`
      // files if they have loaders
      return ["/", "/about", ...slugs.map((slug) => `/product/${slug}`)];
    },
  } satisfies Config;
  
  async function fakeGetSlugsFromCms() {
    await new Promise((r) => setTimeout(r, 1000));
    return ["shirt", "hat"];
  }

• [REMOVE] Allow returning undefined from loaders/actions part 2 (#12057)

  • This is a follow up to Allow returning undefined from actions and loaders #11680 which missed some of the Remix codepaths

• Params, loader data, and action data as props for route component exports (#11961)

  export default function Component({ params, loaderData, actionData }) {}
  
  export function HydrateFallback({ params }) {}
  export function ErrorBoundary({ params, loaderData, actionData }) {}

• Remove duplicate RouterProvider impliementations (#11679)

• Typesafety improvements (#12019)

  React Router now generates types for each of your route modules.
  You can access those types by importing them from ./+types.<route filename without extension>.
  For example:

  // app/routes/product.tsx
  import type * as Route from "./+types.product";
  
  export function loader({ params }: Route.LoaderArgs) {}
  
  export default function Component({ loaderData }: Route.ComponentProps) {}

  This initial implementation targets type inference for:

  • Params : Path parameters from your routing config in routes.ts including file-based routing
  • LoaderData : Loader data from loader and/or clientLoader within your route module
  • ActionData : Action data from action and/or clientAction within your route module

  In the future, we plan to add types for the rest of the route module exports: meta, links, headers, shouldRevalidate, etc.
  We also plan to generate types for typesafe Links:

  <Link to="/products/:id" params={{ id: 1 }} />
  //        ^^^^^^^^^^^^^          ^^^^^^^^^
  // typesafe `to` and `params` based on the available routes in your app

  Check out our docs for more:

  • Explanations > Type Safety
  • How-To > Setting up type safety

• Stabilize unstable_dataStrategy (#11969)

• Stabilize unstable_patchRoutesOnNavigation (#11970)

Patch Changes

• No changes (506329c4e)

• [REMOVE] Changeset to bump pre.4 release (#11871)

• chore: re-enable development warnings through a development exports condition. (#12269)

• Remove unstable upload handler. (#12015)

• [PRERELEASE] Fix typegen for routes with a client loader but no server loader (#12117)

• Remove unneeded dependency on @web3-storage/multipart-parser (#12274)

• Fix redirects returned from loaders/actions using data() (#12021)

• • [PRERELEASE] Fix react-router-serve handling of prerendered HTML files by removing the redirect: false option so it now falls back on the default redirect: true behavior of redirecting from /folder -> /folder/ which will then pick up /folder/index.html from disk. See https://expressjs.com/en/resources/middleware/serve-static.html (#12071)
  • [PRERELEASE] Proxy prerendered loader data into prerender pass for HTML files to avoid double-invocations of the loader at build time

• fix(react-router): (v7) fix static prerender of non-ascii characters (#12161)

• [REMOVE] Rename RemixRouter->DataRouter (#12062)

• Replace substr with substring (#12080)

• Remove the deprecated json utility (#12146)

  • You can use Response.json if you still need to construct JSON responses in your app

• Remove unneeded dependency on source-map (#12275)

@react-router/[email protected]

Major Changes

• For Remix consumers migrating to React Router, the crypto global from the Web Crypto API is now required when using cookie and session APIs. This means that the following APIs are provided from react-router rather than platform-specific packages: (#11837)

  • createCookie
  • createCookieSessionStorage
  • createMemorySessionStorage
  • createSessionStorage

  For consumers running older versions of Node, the installGlobals function from @remix-run/node has been updated to define globalThis.crypto, using Node's require('node:crypto').webcrypto implementation.

  Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:

  • createCookieFactory
  • createSessionStorageFactory
  • createCookieSessionStorageFactory
  • createMemorySessionStorageFactory

Patch Changes

• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]

@react-router/[email protected]

Major Changes

• For Remix consumers migrating to React Router, all exports from @remix-run/cloudflare-pages are now provided for React Router consumers in the @react-router/cloudflare package. There is no longer a separate package for Cloudflare Pages. (#11801)

• For Remix consumers migrating to React Router, the crypto global from the Web Crypto API is now required when using cookie and session APIs. This means that the following APIs are provided from react-router rather than platform-specific packages: (#11837)

  • createCookie
  • createCookieSessionStorage
  • createMemorySessionStorage
  • createSessionStorage

  For consumers running older versions of Node, the installGlobals function from @remix-run/node has been updated to define globalThis.crypto, using Node's require('node:crypto').webcrypto implementation.

  Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:

  • createCookieFactory
  • createSessionStorageFactory
  • createCookieSessionStorageFactory
  • createMemorySessionStorageFactory

Minor Changes

• The @remix-run/cloudflare-workers package has been deprecated. Remix consumers migrating to React Router should use the @react-router/cloudflare package directly. For guidance on how to use @react-router/cloudflare within a Cloudflare Workers context, refer to the Cloudflare Workers template. (#11801)

Patch Changes

• Updated dependencies:
  • [email protected]

@react-router/[email protected]

Major Changes

• For Remix consumers migrating to React Router, the vitePlugin and cloudflareDevProxyVitePlugin exports have been renamed and moved. (#11904)

  -import {
  -  vitePlugin as remix,
  -  cloudflareDevProxyVitePlugin,
  -} from "@remix/dev";
  
  +import { reactRouter } from "@react-router/dev/vite";
  +import { cloudflareDevProxy } from "@react-router/dev/vite/cloudflare";

• Remove single_fetch future flag. (#11522)

• update minimum node version to 18 (#11690)

• Add exports field to all packages (#11675)

• node package no longer re-exports from react-router (#11702)

• For Remix consumers migrating to React Router who used the Vite plugin's buildEnd hook, the resolved reactRouterConfig object no longer contains a publicPath property since this belongs to Vite, not React Router. (#11575)

• For Remix consumers migrating to React Router, the Vite plugin's manifest option has been removed. (#11573)

  The manifest option been superseded by the more powerful buildEnd hook since it's passed the buildManifest argument. You can still write the build manifest to disk if needed, but you'll most likely find it more convenient to write any logic depending on the build manifest within the buildEnd hook itself.

  If you were using the manifest option, you can replace it with a buildEnd hook that writes the manifest to disk like this:

  // react-router.config.ts
  import type { Config } from "@react-router/dev/config";
  import { writeFile } from "node:fs/promises";
  
  export default {
    async buildEnd({ buildManifest }) {
      await writeFile(
        "build/manifest.json",
        JSON.stringify(buildManifest, null, 2),
        "utf-8"
      );
    },
  } satisfies Config;

• • Consolidate types previously duplicated across @remix-run/router, @remix-run/server-runtime, and @remix-run/react now that they all live in react-router (#12177)
    • Examples: LoaderFunction, LoaderFunctionArgs, ActionFunction, ActionFunctionArgs, DataFunctionArgs, RouteManifest, LinksFunction, Route, EntryRoute
    • The RouteManifest type used by the "remix" code is now slightly stricter because it is using the former @remix-run/router RouteManifest
      • Record<string, Route> -> Record<string, Route | undefined>
    • Removed AppData type in favor of inlining unknown in the few locations it was used
    • Removed ServerRuntimeMeta* types in favor of the Meta* types they were duplicated from

• Update default isbot version to v5 and drop support for isbot@3 (#11770)

  • If you have isbot@4 or isbot@5 in your package.json:
    • You do not need to make any changes
  • If you have isbot@3 in your package.json and you have your own entry.server.tsx file in your repo
    • You do not need to make any changes
    • You can upgrade to isbot@5 independent of the React Router v7 upgrade
  • If you have isbot@3 in your package.json and you do not have your own entry.server.tsx file in your repo
    • You are using the internal default entry provided by React Router v7 and you will need to upgrade to isbot@5 in your package.json

• Drop support for Node 18, update minimum Node vestion to 20 (#12171)

  • Remove installGlobals() as this should no longer be necessary

• For Remix consumers migrating to React Router, Vite manifests (i.e. .vite/manifest.json) are now written within each build subdirectory, e.g. build/client/.vite/manifest.json and build/server/.vite/manifest.json instead of build/.vite/client-manifest.json and build/.vite/server-manifest.json. This means that the build output is now much closer to what you'd expect from a typical Vite project. (#11573)

  Originally the Remix Vite plugin moved all Vite manifests to a root-level build/.vite directory to avoid accidentally serving them in production, particularly from the client build. This was later improved with additional logic that deleted these Vite manifest files at the end of the build process unless Vite's build.manifest had been enabled within the app's Vite config. This greatly reduced the risk of accidentally serving the Vite manifests in production since they're only present when explicitly asked for. As a result, we can now assume that consumers will know that they need to manage these additional files themselves, and React Router can safely generate a more standard Vite build output.

Minor Changes

• Params, loader data, and action data as props for route component exports (#11961)

  export default function Component({ params, loaderData, actionData }) {}
  
  export function HydrateFallback({ params }) {}
  export function ErrorBoundary({ params, loaderData, actionData }) {}

• Remove internal entry.server.spa.tsx implementation (#11681)

• Add prefix route config helper to @react-router/dev/routes (#12094)

• Typesafety improvements (#12019)

  React Router now generates types for each of your route modules.
  You can access those types by importing them from ./+types.<route filename without extension>.
  For example:

  // app/routes/product.tsx
  import type * as Route from "./+types.product";
  
  export function loader({ params }: Route.LoaderArgs) {}
  
  export default function Component({ loaderData }: Route.ComponentProps) {}

  This initial implementation targets type inference for:

  • Params : Path parameters from your routing config in routes.ts including file-based routing
  • LoaderData : Loader data from loader and/or clientLoader within your route module
  • ActionData : Action data from action and/or clientAction within your route module

  In the future, we plan to add types for the rest of the route module exports: meta, links, headers, shouldRevalidate, etc.
  We also plan to generate types for typesafe Links:

  <Link to="/products/:id" params={{ id: 1 }} />
  //        ^^^^^^^^^^^^^          ^^^^^^^^^
  // typesafe `to` and `params` based on the available routes in your app

  Check out our docs for more:

  • Explanations > Type Safety
  • How-To > Setting up type safety

Patch Changes

• Enable prerendering for resource routes (#12200)
• chore: warn instead of error for min node version in CLI (#12270)
• chore: re-enable development warnings through a development exports condition. (#12269)
• include root "react-dom" module for optimization (#12060)
• • [PRERELEASE] Fix react-router-serve handling of prerendered HTML files by removing the redirect: false option so it now falls back on the default redirect: true behavior of redirecting from /folder -> /folder/ which will then pick up /folder/index.html from disk. See https://expressjs.com/en/resources/middleware/serve-static.html (#12071)
  • [PRERELEASE] Proxy prerendered loader data into prerender pass for HTML files to avoid double-invocations of the loader at build time
• resolve config directory relative to flat output file structure (#12187)
• if we are in SAP mode, always render the index.html for hydration (#12268)
• fix(react-router): (v7) fix static prerender of non-ascii characters (#12161)
• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]
  • @react-router/[email protected]

[email protected]

Major Changes

• Remove the original defer implementation in favor of using raw promises via single fetch and turbo-stream. This removes these exports from React Router: (#11744)

  • defer
  • AbortedDeferredError
  • type TypedDeferredData
  • UNSAFE_DeferredData
  • UNSAFE_DEFERRED_SYMBOL,

• Use createRemixRouter/RouterProvider in entry.client instead of RemixBrowser (#11469)

• Remove single_fetch future flag. (#11522)

• Remove future.v7_startTransition flag (#11696)

• Remove future.v7_normalizeFormMethod future flag (#11697)

• Allow returning undefined from actions and loaders (#11680)

• update minimum node version to 18 (#11690)

• Remove future.v7_prependBasename from the ionternalized @remix-run/router package (#11726)

• Remove future.v7_throwAbortReason from internalized @remix-run/router package (#11728)

• Add exports field to all packages (#11675)

• node package no longer re-exports from react-router (#11702)

• updates the minimum React version to 18 (#11689)

• • Remove the future.v7_partialHydration flag (#11725)
    • This also removes the <RouterProvider fallbackElement> prop
      • To migrate, move the fallbackElement to a hydrateFallbackElement/HydrateFallback on your root route
    • Also worth nothing there is a related breaking changer with this future flag:
      • Without future.v7_partialHydration (when using fallbackElement), state.navigation was populated during the initial load
      • With future.v7_partialHydration, state.navigation remains in an "idle" state during the initial load

• Remove future.v7_fetcherPersist flag (#11731)

Minor Changes

• Add prefetching support to Link/NavLink when using Remix SSR (#11402)
• Enhance ScrollRestoration so it can restore properly on an SSR'd document load (#11401)
• Add built-in Remix-style hydration support to RouterProvider. When running from a Remix-SSR'd HTML payload with the proper window variables (__remixContext, __remixManifest, __remixRouteModules), you don't need to pass a router prop and RouterProvider will create the router for you internally. (#11396) (#11400)

Patch Changes

• Memoize some RouterProvider internals to reduce uneccesary re-renders (#11817)
• Updated dependencies:
  • [email protected]

@react-router/[email protected]

Major Changes

• Remove single_fetch future flag. (#11522)

• update minimum node version to 18 (#11690)

• Add exports field to all packages (#11675)

• node package no longer re-exports from react-router (#11702)

• Drop support for Node 18, update minimum Node vestion to 20 (#12171)

  • Remove installGlobals() as this should no longer be necessary

Patch Changes

• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]

@react-router/[email protected]

Major Changes

• Remove single_fetch future flag. (#11522)

• For Remix consumers migrating to React Router, the crypto global from the Web Crypto API is now required when using cookie and session APIs. This means that the following APIs are provided from react-router rather than platform-specific packages: (#11837)

  • createCookie
  • createCookieSessionStorage
  • createMemorySessionStorage
  • createSessionStorage

  For consumers running older versions of Node, the installGlobals function from @remix-run/node has been updated to define globalThis.crypto, using Node's require('node:crypto').webcrypto implementation.

  Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:

  • createCookieFactory
  • createSessionStorageFactory
  • createCookieSessionStorageFactory
  • createMemorySessionStorageFactory

• update minimum node version to 18 (#11690)

• Add exports field to all packages (#11675)

• node package no longer re-exports from react-router (#11702)

• Drop support for Node 18, update minimum Node vestion to 20 (#12171)

  • Remove installGlobals() as this should no longer be necessary

Patch Changes

• Add createRequestListener to @react-router/node (#12319)
• Remove unstable upload handler. (#12015)
• Remove unneeded dependency on @web3-storage/multipart-parser (#12274)
• Updated dependencies:
  • [email protected]

@react-router/[email protected]

Major Changes

• Remove single_fetch future flag. (#11522)
• update minimum node version to 18 (#11690)
• Add exports field to all packages (#11675)
• node package no longer re-exports from react-router (#11702)

Patch Changes

• • [PRERELEASE] Fix react-router-serve handling of prerendered HTML files by removing the redirect: false option so it now falls back on the default redirect: true behavior of redirecting from /folder -> /folder/ which will then pick up /folder/index.html from disk. See https://expressjs.com/en/resources/middleware/serve-static.html (#12071)
  • [PRERELEASE] Proxy prerendered loader data into prerender pass for HTML files to avoid double-invocations of the loader at build time

• Update express.static configurations to support prerendering (#11547)

  • Assets in the build/client/assets folder are served as before, with a 1-year immutable Cache-Control header
  • Static files outside of assets, such as pre-rendered .html and .data files are not served with a specific Cache-Control header
  • .data files are served with Content-Type: text/x-turbo
    • For some reason, when adding this via express.static, it seems to also add a Cache-Control: public, max-age=0 to .data files

• Updated dependencies:

  • [email protected]
  • @react-router/[email protected]
  • @react-router/[email protected]

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • @react-router/[email protected]

@react-router/[email protected]

Patch Changes

• Updated dependencies:
  • @react-router/[email protected]

[email protected]