react-router 8.4.0 → 8.5.0

package/docs/start/framework/navigating.md

@@ -44,10 +44,6 @@ a.active {
 a.pending {
   animate: pulse 1s infinite;
 }
-
-a.transitioning {
-  /* css transition is running */
-}
 ```
 
 It also has callback props on `className`, `style`, and `children` with the states for inline styling or conditional rendering:
@@ -56,11 +52,10 @@ It also has callback props on `className`, `style`, and `children` with the stat
 // className
 <NavLink
   to="/messages"
-  className={({ isActive, isPending, isTransitioning }) =>
+  className={({ isActive, isPending }) =>
     [
       isPending ? "pending" : "",
       isActive ? "active" : "",
-      isTransitioning ? "transitioning" : "",
     ].join(" ")
   }
 >
@@ -72,11 +67,10 @@ It also has callback props on `className`, `style`, and `children` with the stat
 // style
 <NavLink
   to="/messages"
-  style={({ isActive, isPending, isTransitioning }) => {
+  style={({ isActive, isPending }) => {
     return {
       fontWeight: isActive ? "bold" : "",
       color: isPending ? "red" : "black",
-      viewTransitionName: isTransitioning ? "slide" : "",
     };
   }}
 >
@@ -87,12 +81,14 @@ It also has callback props on `className`, `style`, and `children` with the stat
 ```tsx
 // children
 <NavLink to="/tasks">
-  {({ isActive, isPending, isTransitioning }) => (
+  {({ isActive }) => (
     <span className={isActive ? "active" : ""}>Tasks</span>
   )}
 </NavLink>
 ```
 
+For animated navigations, see [View Transitions](../../how-to/view-transitions). The legacy `isTransitioning` render prop and `transitioning` class are deprecated in favor of React's `<ViewTransition>` component.
+
 ## Link
 
 Use `<Link>` when the link doesn't need active styling:

package/docs/start/framework/rendering.md

@@ -54,6 +54,43 @@ export default {
 
 Pre-rendering is a build-time operation that generates static HTML and client navigation data payloads for a list of URLs. This is useful for SEO and performance, especially for deployments without server rendering. When pre-rendering, route module loaders are used to fetch data at build time.
 
+## API-only Mode (unstable)
+
+<docs-warning>API-only Mode is experimental and may change in minor or patch releases. It is not supported in RSC Framework Mode.</docs-warning>
+
+Set `ssr: "unstable_api-only"` to keep a runtime server for loaders, actions, and route discovery while disabling production server-side document rendering:
+
+```ts filename=react-router.config.ts
+import type { Config } from "@react-router/dev/config";
+
+export default {
+  ssr: "unstable_api-only",
+} satisfies Config;
+```
+
+Without prerendering, the build generates a root-only `index.html` shell using the root `HydrateFallback`, like [SPA Mode](../../how-to/spa). The browser fetches server loader data as it initializes the page. Routes can use server `loader` and `action` exports without requiring `clientLoader` or `clientAction` wrappers. Lazy route discovery remains enabled by default.
+
+You can also [combine API-only Mode with prerendering](../../how-to/pre-rendering#pre-rendering-with-api-only-mode-unstable) to serve complete HTML for selected paths and a SPA fallback for other paths.
+
+Deploy both `build/client` and the runtime server build. Serve assets, prerendered documents, and the SPA fallback from the client build; send `.data` and route discovery requests (`/__manifest` by default) to the React Router request handler. The production API-only handler returns `404` for document requests. `react-router-serve` handles this routing automatically.
+
+### Using a separate API origin
+
+By default, data and route discovery requests use the same origin as the client application. Set `unstable_apiServerOrigin` to use a separate API server:
+
+```ts filename=react-router.config.ts
+import type { Config } from "@react-router/dev/config";
+
+export default {
+  ssr: "unstable_api-only",
+  unstable_apiServerOrigin: "https://api.example.com",
+} satisfies Config;
+```
+
+This option applies to loader, action, and route discovery requests only in API-only Mode. Use an origin without a path, query, or hash. Configure CORS on the API server and allow the client origin via [`allowedActionOrigins`](../../api/framework-conventions/react-router.config.ts#allowedactionorigins) for cross-origin action submissions. Requests use the browser's default `same-origin` credential policy; this option does not enable sending cookies to a different origin.
+
+To customize JavaScript-issued requests with authentication headers or cross-origin credentials, see [Custom Fetch](../../how-to/custom-fetch). Native data prefetches bypass custom fetch.
+
 ---
 
 Next: [Data Loading](./data-loading)

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "react-router",
   "type": "module",
-  "version": "8.4.0",
+  "version": "8.5.0",
   "description": "Declarative routing for React",
   "keywords": [
     "react",
@@ -104,10 +104,18 @@
     "wireit": "0.14.12"
   },
   "peerDependencies": {
+    "@types/react": ">=19.2.0",
+    "@types/react-dom": ">=19.2.0",
     "react": ">=19.2.7",
     "react-dom": ">=19.2.7"
   },
   "peerDependenciesMeta": {
+    "@types/react": {
+      "optional": true
+    },
+    "@types/react-dom": {
+      "optional": true
+    },
     "react-dom": {
       "optional": true
     }