react-router 0.0.0-experimental-e56aa53bc → 0.0.0-experimental-e6fb6e074

package/CHANGELOG.md

@@ -1,766 +1,50 @@
 # `react-router`
 
-## 7.5.1
-
-### Patch Changes
-
-- Fix single fetch bug where no revalidation request would be made when navigating upwards to a reused parent route ([#13253](https://github.com/remix-run/react-router/pull/13253))
-
-- When using the object-based `route.lazy` API, the `HydrateFallback` and `hydrateFallbackElement` properties are now skipped when lazy loading routes after hydration. ([#13376](https://github.com/remix-run/react-router/pull/13376))
-
-  If you move the code for these properties into a separate file, you can use this optimization to avoid downloading unused hydration code. For example:
-
-  ```ts
-  createBrowserRouter([
-    {
-      path: "/show/:showId",
-      lazy: {
-        loader: async () => (await import("./show.loader.js")).loader,
-        Component: async () => (await import("./show.component.js")).Component,
-        HydrateFallback: async () =>
-          (await import("./show.hydrate-fallback.js")).HydrateFallback,
-      },
-    },
-  ]);
-  ```
-
-- Properly revalidate prerendered paths when param values change ([#13380](https://github.com/remix-run/react-router/pull/13380))
-
-- UNSTABLE: Add a new `unstable_runClientMiddleware` argument to `dataStrategy` to enable middleware execution in custom `dataStrategy` implementations ([#13395](https://github.com/remix-run/react-router/pull/13395))
-
-- UNSTABLE: Add better error messaging when `getLoadContext` is not updated to return a `Map`" ([#13242](https://github.com/remix-run/react-router/pull/13242))
-
-- Do not automatically add `null` to `staticHandler.query()` `context.loaderData` if routes do not have loaders ([#13223](https://github.com/remix-run/react-router/pull/13223))
-
-  - This was a Remix v2 implementation detail inadvertently left in for React Router v7
-  - Now that we allow returning `undefined` from loaders, our prior check of `loaderData[routeId] !== undefined` was no longer sufficient and was changed to a `routeId in loaderData` check - these `null` values can cause issues for this new check
-  - ⚠️ This could be a "breaking bug fix" for you if you are doing manual SSR with `createStaticHandler()`/`<StaticRouterProvider>`, and using `context.loaderData` to control `<RouterProvider>` hydration behavior on the client
-
-- Fix prerendering when a loader returns a redirect ([#13365](https://github.com/remix-run/react-router/pull/13365))
-
-- UNSTABLE: Update context type for `LoaderFunctionArgs`/`ActionFunctionArgs` when middleware is enabled ([#13381](https://github.com/remix-run/react-router/pull/13381))
-
-- Add support for the new `unstable_shouldCallHandler`/`unstable_shouldRevalidateArgs` APIs in `dataStrategy` ([#13253](https://github.com/remix-run/react-router/pull/13253))
-
-## 7.5.0
-
-### Minor Changes
-
-- Add granular object-based API for `route.lazy` to support lazy loading of individual route properties, for example: ([#13294](https://github.com/remix-run/react-router/pull/13294))
-
-  ```ts
-  createBrowserRouter([
-    {
-      path: "/show/:showId",
-      lazy: {
-        loader: async () => (await import("./show.loader.js")).loader,
-        action: async () => (await import("./show.action.js")).action,
-        Component: async () => (await import("./show.component.js")).Component,
-      },
-    },
-  ]);
-  ```
-
-  **Breaking change for `route.unstable_lazyMiddleware` consumers**
-
-  The `route.unstable_lazyMiddleware` property is no longer supported. If you want to lazily load middleware, you must use the new object-based `route.lazy` API with `route.lazy.unstable_middleware`, for example:
-
-  ```ts
-  createBrowserRouter([
-    {
-      path: "/show/:showId",
-      lazy: {
-        unstable_middleware: async () =>
-          (await import("./show.middleware.js")).middleware,
-        // etc.
-      },
-    },
-  ]);
-  ```
-
-### Patch Changes
-
-- Introduce `unstable_subResourceIntegrity` future flag that enables generation of an importmap with integrity for the scripts that will be loaded by the browser. ([#13163](https://github.com/remix-run/react-router/pull/13163))
-
-## 7.4.1
-
-### Patch Changes
-
-- Fix types on `unstable_MiddlewareFunction` to avoid type errors when a middleware doesn't return a value ([#13311](https://github.com/remix-run/react-router/pull/13311))
-- Dedupe calls to `route.lazy` functions ([#13260](https://github.com/remix-run/react-router/pull/13260))
-- Add support for `route.unstable_lazyMiddleware` function to allow lazy loading of middleware logic. ([#13210](https://github.com/remix-run/react-router/pull/13210))
-
-  **Breaking change for `unstable_middleware` consumers**
-
-  The `route.unstable_middleware` property is no longer supported in the return value from `route.lazy`. If you want to lazily load middleware, you must use `route.unstable_lazyMiddleware`.
-
-## 7.4.0
-
-### Patch Changes
-
-- Fix root loader data on initial load redirects in SPA mode ([#13222](https://github.com/remix-run/react-router/pull/13222))
-- Load ancestor pathless/index routes in lazy route discovery for upwards non-eager-discoery routing ([#13203](https://github.com/remix-run/react-router/pull/13203))
-- Fix `shouldRevalidate` behavior for `clientLoader`-only routes in `ssr:true` apps ([#13221](https://github.com/remix-run/react-router/pull/13221))
-- UNSTABLE: Fix `RequestHandler` `loadContext` parameter type when middleware is enabled ([#13204](https://github.com/remix-run/react-router/pull/13204))
-- UNSTABLE: Update `Route.unstable_MiddlewareFunction` to have a return value of `Response | undefined` instead of `Response | void` becaue you should not return anything if you aren't returning the `Response` ([#13199](https://github.com/remix-run/react-router/pull/13199))
-- UNSTABLE(BREAKING): If a middleware throws an error, ensure we only bubble the error itself via `next()` and are no longer leaking the `MiddlewareError` implementation detail ([#13180](https://github.com/remix-run/react-router/pull/13180))
-
-## 7.3.0
+## 6.30.0
 
 ### Minor Changes
 
-- Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13061](https://github.com/remix-run/react-router/pull/13061))
-
-  - In framework mode, Lazy Route Discovery will now detect manifest version mismatches after a new deploy
-  - On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path
-  - On `fetcher` calls to undiscovered routes, this mismatch will trigger a document reload of the current path
+- Add `fetcherKey` as a parameter to `patchRoutesOnNavigation` ([#13109](https://github.com/remix-run/react-router/pull/13109))
 
 ### Patch Changes
 
-- Skip resource route flow in dev server in SPA mode ([#13113](https://github.com/remix-run/react-router/pull/13113))
-
-- Support middleware on routes (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941))
-
-  Middleware is implemented behind a `future.unstable_middleware` flag. To enable, you must enable the flag and the types in your `react-router-config.ts` file:
-
-  ```ts
-  import type { Config } from "@react-router/dev/config";
-  import type { Future } from "react-router";
-
-  declare module "react-router" {
-    interface Future {
-      unstable_middleware: true; // 👈 Enable middleware types
-    }
-  }
-
-  export default {
-    future: {
-      unstable_middleware: true, // 👈 Enable middleware
-    },
-  } satisfies Config;
-  ```
-
-  ⚠️ Middleware is unstable and should not be adopted in production. There is at least one known de-optimization in route module loading for `clientMiddleware` that we will be addressing this before a stable release.
-
-  ⚠️ Enabling middleware contains a breaking change to the `context` parameter passed to your `loader`/`action` functions - see below for more information.
-
-  Once enabled, routes can define an array of middleware functions that will run sequentially before route handlers run. These functions accept the same parameters as `loader`/`action` plus an additional `next` parameter to run the remaining data pipeline. This allows middlewares to perform logic before and after handlers execute.
-
-  ```tsx
-  // Framework mode
-  export const unstable_middleware = [serverLogger, serverAuth]; // server
-  export const unstable_clientMiddleware = [clientLogger]; // client
-
-  // Library mode
-  const routes = [
-    {
-      path: "/",
-      // Middlewares are client-side for library mode SPA's
-      unstable_middleware: [clientLogger, clientAuth],
-      loader: rootLoader,
-      Component: Root,
-    },
-  ];
-  ```
-
-  Here's a simple example of a client-side logging middleware that can be placed on the root route:
-
-  ```tsx
-  const clientLogger: Route.unstable_ClientMiddlewareFunction = async (
-    { request },
-    next
-  ) => {
-    let start = performance.now();
-
-    // Run the remaining middlewares and all route loaders
-    await next();
-
-    let duration = performance.now() - start;
-    console.log(`Navigated to ${request.url} (${duration}ms)`);
-  };
-  ```
-
-  Note that in the above example, the `next`/`middleware` functions don't return anything. This is by design as on the client there is no "response" to send over the network like there would be for middlewares running on the server. The data is all handled behind the scenes by the stateful `router`.
-
-  For a server-side middleware, the `next` function will return the HTTP `Response` that React Router will be sending across the wire, thus giving you a chance to make changes as needed. You may throw a new response to short circuit and respond immediately, or you may return a new or altered response to override the default returned by `next()`.
-
-  ```tsx
-  const serverLogger: Route.unstable_MiddlewareFunction = async (
-    { request, params, context },
-    next
-  ) => {
-    let start = performance.now();
-
-    // 👇 Grab the response here
-    let res = await next();
-
-    let duration = performance.now() - start;
-    console.log(`Navigated to ${request.url} (${duration}ms)`);
-
-    // 👇 And return it here (optional if you don't modify the response)
-    return res;
-  };
-  ```
-
-  You can throw a `redirect` from a middleware to short circuit any remaining processing:
-
-  ```tsx
-  import { sessionContext } from "../context";
-  const serverAuth: Route.unstable_MiddlewareFunction = (
-    { request, params, context },
-    next
-  ) => {
-    let session = context.get(sessionContext);
-    let user = session.get("user");
-    if (!user) {
-      session.set("returnTo", request.url);
-      throw redirect("/login", 302);
-    }
-  };
-  ```
-
-  _Note that in cases like this where you don't need to do any post-processing you don't need to call the `next` function or return a `Response`._
-
-  Here's another example of using a server middleware to detect 404s and check the CMS for a redirect:
-
-  ```tsx
-  const redirects: Route.unstable_MiddlewareFunction = async ({
-    request,
-    next,
-  }) => {
-    // attempt to handle the request
-    let res = await next();
-
-    // if it's a 404, check the CMS for a redirect, do it last
-    // because it's expensive
-    if (res.status === 404) {
-      let cmsRedirect = await checkCMSRedirects(request.url);
-      if (cmsRedirect) {
-        throw redirect(cmsRedirect, 302);
-      }
-    }
-
-    return res;
-  };
-  ```
-
-  **`context` parameter**
-
-  When middleware is enabled, your application will use a different type of `context` parameter in your loaders and actions to provide better type safety. Instead of `AppLoadContext`, `context` will now be an instance of `ContextProvider` that you can use with type-safe contexts (similar to `React.createContext`):
-
-  ```ts
-  import { unstable_createContext } from "react-router";
-  import { Route } from "./+types/root";
-  import type { Session } from "./sessions.server";
-  import { getSession } from "./sessions.server";
-
-  let sessionContext = unstable_createContext<Session>();
-
-  const sessionMiddleware: Route.unstable_MiddlewareFunction = ({
-    context,
-    request,
-  }) => {
-    let session = await getSession(request);
-    context.set(sessionContext, session);
-    //                          ^ must be of type Session
-  };
-
-  // ... then in some downstream middleware
-  const loggerMiddleware: Route.unstable_MiddlewareFunction = ({
-    context,
-    request,
-  }) => {
-    let session = context.get(sessionContext);
-    //  ^ typeof Session
-    console.log(session.get("userId"), request.method, request.url);
-  };
-
-  // ... or some downstream loader
-  export function loader({ context }: Route.LoaderArgs) {
-    let session = context.get(sessionContext);
-    let profile = await getProfile(session.get("userId"));
-    return { profile };
-  }
-  ```
-
-  If you are using a custom server with a `getLoadContext` function, the return value for initial context values passed from the server adapter layer is no longer an object and should now return an `unstable_InitialContext` (`Map<RouterContext, unknown>`):
-
-  ```ts
-  let adapterContext = unstable_createContext<MyAdapterContext>();
-
-  function getLoadContext(req, res): unstable_InitialContext {
-    let map = new Map();
-    map.set(adapterContext, getAdapterContext(req));
-    return map;
-  }
-  ```
-
-- Fix types for loaderData and actionData that contained `Record`s ([#13139](https://github.com/remix-run/react-router/pull/13139))
-
-  UNSTABLE(BREAKING):
-
-  `unstable_SerializesTo` added a way to register custom serialization types in Single Fetch for other library and framework authors like Apollo.
-  It was implemented with branded type whose branded property that was made optional so that casting arbitrary values was easy:
-
-  ```ts
-  // without the brand being marked as optional
-  let x1 = 42 as unknown as unstable_SerializesTo<number>;
-  //          ^^^^^^^^^^
-
-  // with the brand being marked as optional
-  let x2 = 42 as unstable_SerializesTo<number>;
-  ```
-
-  However, this broke type inference in `loaderData` and `actionData` for any `Record` types as those would now (incorrectly) match `unstable_SerializesTo`.
-  This affected all users, not just those that depended on `unstable_SerializesTo`.
-  To fix this, the branded property of `unstable_SerializesTo` is marked as required instead of optional.
-
-  For library and framework authors using `unstable_SerializesTo`, you may need to add `as unknown` casts before casting to `unstable_SerializesTo`.
-
-- \[REMOVE] Remove middleware depth logic and always call middlware for all matches ([#13172](https://github.com/remix-run/react-router/pull/13172))
-
-- Fix single fetch `_root.data` requests when a `basename` is used ([#12898](https://github.com/remix-run/react-router/pull/12898))
-
-- Add `context` support to client side data routers (unstable) ([#12941](https://github.com/remix-run/react-router/pull/12941))
-
-  Your application `loader` and `action` functions on the client will now receive a `context` parameter. This is an instance of `unstable_RouterContextProvider` that you use with type-safe contexts (similar to `React.createContext`) and is most useful with the corresponding `middleware`/`clientMiddleware` API's:
-
-  ```ts
-  import { unstable_createContext } from "react-router";
-
-  type User = {
-    /*...*/
-  };
-
-  let userContext = unstable_createContext<User>();
-
-  function sessionMiddleware({ context }) {
-    let user = await getUser();
-    context.set(userContext, user);
-  }
-
-  // ... then in some downstream loader
-  function loader({ context }) {
-    let user = context.get(userContext);
-    let profile = await getProfile(user.id);
-    return { profile };
-  }
-  ```
-
-  Similar to server-side requests, a fresh `context` will be created per navigation (or `fetcher` call). If you have initial data you'd like to populate in the context for every request, you can provide an `unstable_getContext` function at the root of your app:
-
-  - Library mode - `createBrowserRouter(routes, { unstable_getContext })`
-  - Framework mode - `<HydratedRouter unstable_getContext>`
-
-  This function should return an value of type `unstable_InitialContext` which is a `Map<unstable_RouterContext, unknown>` of context's and initial values:
-
-  ```ts
-  const loggerContext = unstable_createContext<(...args: unknown[]) => void>();
-
-  function logger(...args: unknown[]) {
-    console.log(new Date.toISOString(), ...args);
-  }
-
-  function unstable_getContext() {
-    let map = new Map();
-    map.set(loggerContext, logger);
-    return map;
-  }
-  ```
+- Updated dependencies:
+  - `@remix-run/router@1.23.0`
 
-## 7.2.0
+## 6.29.0
 
 ### Minor Changes
 
-- New type-safe `href` utility that guarantees links point to actual paths in your app ([#13012](https://github.com/remix-run/react-router/pull/13012))
+- Provide the request `signal` as a parameter to `patchRoutesOnNavigation` ([#12900](https://github.com/remix-run/react-router/pull/12900))
 
-  ```tsx
-  import { href } from "react-router";
-
-  export default function Component() {
-    const link = href("/blog/:slug", { slug: "my-first-post" });
-    return (
-      <main>
-        <Link to={href("/products/:id", { id: "asdf" })} />
-        <NavLink to={href("/:lang?/about", { lang: "en" })} />
-      </main>
-    );
-  }
-  ```
+  - This can be used to abort any manifest fetches if the in-flight navigation/fetcher is aborted
 
 ### Patch Changes
 
-- Fix typegen for repeated params ([#13012](https://github.com/remix-run/react-router/pull/13012))
-
-  In React Router, path parameters are keyed by their name.
-  So for a path pattern like `/a/:id/b/:id?/c/:id`, the last `:id` will set the value for `id` in `useParams` and the `params` prop.
-  For example, `/a/1/b/2/c/3` will result in the value `{ id: 3 }` at runtime.
-
-  Previously, generated types for params incorrectly modeled repeated params with an array.
-  So `/a/1/b/2/c/3` generated a type like `{ id: [1,2,3] }`.
-
-  To be consistent with runtime behavior, the generated types now correctly model the "last one wins" semantics of path parameters.
-  So `/a/1/b/2/c/3` now generates a type like `{ id: 3 }`.
-
-- Don't apply Single Fetch revalidation de-optimization when in SPA mode since there is no server HTTP request ([#12948](https://github.com/remix-run/react-router/pull/12948))
-
-- Properly handle revalidations to across a prerender/SPA boundary ([#13021](https://github.com/remix-run/react-router/pull/13021))
-
-  - In "hybrid" applications where some routes are pre-rendered and some are served from a SPA fallback, we need to avoid making `.data` requests if the path wasn't pre-rendered because the request will 404
-  - We don't know all the pre-rendered paths client-side, however:
-    - All `loader` data in `ssr:false` mode is static because it's generated at build time
-    - A route must use a `clientLoader` to do anything dynamic
-    - Therefore, if a route only has a `loader` and not a `clientLoader`, we disable revalidation by default because there is no new data to retrieve
-    - We short circuit and skip single fetch `.data` request logic if there are no server loaders with `shouldLoad=true` in our single fetch `dataStrategy`
-    - This ensures that the route doesn't cause a `.data` request that would 404 after a submission
-
-- Error at build time in `ssr:false` + `prerender` apps for the edge case scenario of: ([#13021](https://github.com/remix-run/react-router/pull/13021))
-
-  - A parent route has only a `loader` (does not have a `clientLoader`)
-  - The parent route is pre-rendered
-  - The parent route has children routes which are not prerendered
-  - This means that when the child paths are loaded via the SPA fallback, the parent won't have any `loaderData` because there is no server on which to run the `loader`
-  - This can be resolved by either adding a parent `clientLoader` or pre-rendering the child paths
-  - If you add a `clientLoader`, calling the `serverLoader()` on non-prerendered paths will throw a 404
-
-- Add unstable support for splitting route modules in framework mode via `future.unstable_splitRouteModules` ([#11871](https://github.com/remix-run/react-router/pull/11871))
-
-- Add `unstable_SerializesTo` brand type for library authors to register types serializable by React Router's streaming format (`turbo-stream`) ([`ab5b05b02`](https://github.com/remix-run/react-router/commit/ab5b05b02f99f062edb3c536c392197c88eb6c77))
-
-- Align dev server behavior with static file server behavior when `ssr:false` is set ([#12948](https://github.com/remix-run/react-router/pull/12948))
-
-  - When no `prerender` config exists, only SSR down to the root `HydrateFallback` (SPA Mode)
-  - When a `prerender` config exists but the current path is not prerendered, only SSR down to the root `HydrateFallback` (SPA Fallback)
-  - Return a 404 on `.data` requests to non-pre-rendered paths
-
-- Improve prefetch performance of CSS side effects in framework mode ([#12889](https://github.com/remix-run/react-router/pull/12889))
-
-- Disable Lazy Route Discovery for all `ssr:false` apps and not just "SPA Mode" because there is no runtime server to serve the search-param-configured `__manifest` requests ([#12894](https://github.com/remix-run/react-router/pull/12894))
-
-  - We previously only disabled this for "SPA Mode" which is `ssr:false` and no `prerender` config but we realized it should apply to all `ssr:false` apps, including those prerendering multiple pages
-  - In those `prerender` scenarios we would prerender the `/__manifest` file assuming the static file server would serve it but that makes some unneccesary assumptions about the static file server behaviors
-
-- Properly handle interrupted manifest requests in lazy route discovery ([#12915](https://github.com/remix-run/react-router/pull/12915))
-
-## 7.1.5
-
-### Patch Changes
-
-- Fix regression introduced in `7.1.4` via [#12800](https://github.com/remix-run/react-router/pull/12800) that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (`patchRoutesOnNavigation`) ([#12927](https://github.com/remix-run/react-router/pull/12927))
-
-## 7.1.4
-
-### Patch Changes
-
-- Internal reorg to clean up some duplicated route module types ([#12799](https://github.com/remix-run/react-router/pull/12799))
-- Properly handle status codes that cannot have a body in single fetch responses (204, etc.) ([#12760](https://github.com/remix-run/react-router/pull/12760))
-- Stop erroring on resource routes that return raw strings/objects and instead serialize them as `text/plain` or `application/json` responses ([#12848](https://github.com/remix-run/react-router/pull/12848))
-  - This only applies when accessed as a resource route without the `.data` extension
-  - When accessed from a Single Fetch `.data` request, they will still be encoded via `turbo-stream`
-- Optimize Lazy Route Discovery path discovery to favor a single `querySelectorAll` call at the `body` level instead of many calls at the sub-tree level ([#12731](https://github.com/remix-run/react-router/pull/12731))
-- Properly bubble headers as `errorHeaders` when throwing a `data()` result ([#12846](https://github.com/remix-run/react-router/pull/12846))
-  - Avoid duplication of `Set-Cookie` headers could be duplicated if also returned from `headers`
-- Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12800](https://github.com/remix-run/react-router/pull/12800))
-
-## 7.1.3
-
-_No changes_
-
-## 7.1.2
-
-### Patch Changes
-
-- Fix issue with fetcher data cleanup in the data layer on fetcher unmount ([#12681](https://github.com/remix-run/react-router/pull/12681))
-- Do not rely on `symbol` for filtering out `redirect` responses from loader data ([#12694](https://github.com/remix-run/react-router/pull/12694))
-
-  Previously, some projects were getting type checking errors like:
-
-  ```ts
-  error TS4058: Return type of exported function has or is using name 'redirectSymbol' from external module "node_modules/..." but cannot be named.
-  ```
-
-  Now that `symbol`s are not used for the `redirect` response type, these errors should no longer be present.
-
-## 7.1.1
-
-_No changes_
-
-## 7.1.0
-
-### Patch Changes
-
-- Throw unwrapped single fetch redirect to align with pre-single fetch behavior ([#12506](https://github.com/remix-run/react-router/pull/12506))
-- Ignore redirects when inferring loader data types ([#12527](https://github.com/remix-run/react-router/pull/12527))
-- Remove `<Link prefetch>` warning which suffers from false positives in a lazy route discovery world ([#12485](https://github.com/remix-run/react-router/pull/12485))
+- Do not log v7 deprecation warnings in production builds ([#12794](https://github.com/remix-run/react-router/pull/12794))
+- Limit matchRoutes optimization to client side routers ([#12881](https://github.com/remix-run/react-router/pull/12881))
+- Optimize route matching by skipping redundant `matchRoutes` calls when possible ([#12169](https://github.com/remix-run/react-router/pull/12169))
+- Updated dependencies:
+  - `@remix-run/router@1.22.0`
 
-## 7.0.2
+## 6.28.2
 
 ### Patch Changes
 
-- temporarily only use one build in export map so packages can have a peer dependency on react router ([#12437](https://github.com/remix-run/react-router/pull/12437))
-- Generate wide `matches` and `params` types for current route and child routes ([#12397](https://github.com/remix-run/react-router/pull/12397))
-
-  At runtime, `matches` includes child route matches and `params` include child route path parameters.
-  But previously, we only generated types for parent routes in `matches`; for `params`, we only considered the parent routes and the current route.
-  To align our generated types more closely to the runtime behavior, we now generate more permissive, wider types when accessing child route information.
-
-## 7.0.1
-
-_No changes_
-
-## 7.0.0
-
-### 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](https://github.com/remix-run/react-router/pull/11744))
-
-  - `defer`
-  - `AbortedDeferredError`
-  - `type TypedDeferredData`
-  - `UNSAFE_DeferredData`
-  - `UNSAFE_DEFERRED_SYMBOL`,
-
-- - Collapse `@remix-run/router` into `react-router` ([#11505](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/11522))
-
-- Drop support for Node 16, React Router SSR now requires Node 18 or higher ([#11391](https://github.com/remix-run/react-router/pull/11391))
-
-- Remove `future.v7_startTransition` flag ([#11696](https://github.com/remix-run/react-router/pull/11696))
-
-- - Expose the underlying router promises from the following APIs for compsition in React 19 APIs: ([#11521](https://github.com/remix-run/react-router/pull/11521))
-    - `useNavigate()`
-    - `useSubmit`
-    - `useFetcher().load`
-    - `useFetcher().submit`
-    - `useRevalidator.revalidate`
-
-- Remove `future.v7_normalizeFormMethod` future flag ([#11697](https://github.com/remix-run/react-router/pull/11697))
-
-- For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/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](https://github.com/remix-run/react-router/pull/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.](https://nodejs.org/api/webcrypto.html)
-
-  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](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/11690))
-
-- Remove `future.v7_prependBasename` from the ionternalized `@remix-run/router` package ([#11726](https://github.com/remix-run/react-router/pull/11726))
-
-- Migrate Remix type generics to React Router ([#12180](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/11728))
-
-- Add `exports` field to all packages ([#11675](https://github.com/remix-run/react-router/pull/11675))
-
-- node package no longer re-exports from react-router ([#11702](https://github.com/remix-run/react-router/pull/11702))
-
-- renamed RemixContext to FrameworkContext ([#11705](https://github.com/remix-run/react-router/pull/11705))
-
-- updates the minimum React version to 18 ([#11689](https://github.com/remix-run/react-router/pull/11689))
-
-- PrefetchPageDescriptor replaced by PageLinkDescriptor ([#11960](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/11695))
-
-- Drop support for Node 18, update minimum Node vestion to 20 ([#12171](https://github.com/remix-run/react-router/pull/12171))
-
-  - Remove `installGlobals()` as this should no longer be necessary
-
-- Remove remaining future flags ([#11820](https://github.com/remix-run/react-router/pull/11820))
-
-  - React Router `v7_skipActionErrorRevalidation`
-  - Remix `v3_fetcherPersist`, `v3_relativeSplatPath`, `v3_throwAbortReason`
-
-- rename createRemixStub to createRoutesStub ([#11692](https://github.com/remix-run/react-router/pull/11692))
-
-- Remove `@remix-run/router` deprecated `detectErrorBoundary` option in favor of `mapRouteProperties` ([#11751](https://github.com/remix-run/react-router/pull/11751))
-
-- Add `react-router/dom` subpath export to properly enable `react-dom` as an optional `peerDependency` ([#11851](https://github.com/remix-run/react-router/pull/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](https://github.com/remix-run/react-router/pull/11731))
-
-- Update `cookie` dependency to `^1.0.1` - please see the [release notes](https://github.com/jshttp/cookie/releases) for any breaking changes ([#12172](https://github.com/remix-run/react-router/pull/12172))
-
-### Minor Changes
-
-- - Add support for `prerender` config in the React Router vite plugin, to support existing SSG use-cases ([#11539](https://github.com/remix-run/react-router/pull/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.
-
-  ```ts
-  // 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"];
-  }
-  ```
-
-- Params, loader data, and action data as props for route component exports ([#11961](https://github.com/remix-run/react-router/pull/11961))
-
-  ```tsx
-  export default function Component({ params, loaderData, actionData }) {}
-
-  export function HydrateFallback({ params }) {}
-  export function ErrorBoundary({ params, loaderData, actionData }) {}
-  ```
-
-- Remove duplicate `RouterProvider` impliementations ([#11679](https://github.com/remix-run/react-router/pull/11679))
-
-- ### Typesafety improvements ([#12019](https://github.com/remix-run/react-router/pull/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:
-
-  ```ts
-  // 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 `Link`s:
-
-  ```tsx
-  <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_](https://reactrouter.com/dev/guides/explanation/type-safety)
-  - [_How-To > Setting up type safety_](https://reactrouter.com/dev/guides/how-to/setting-up-type-safety)
-
-- Stabilize `unstable_dataStrategy` ([#11969](https://github.com/remix-run/react-router/pull/11969))
+- Updated dependencies:
+  - `@remix-run/router@1.21.1`
 
-- Stabilize `unstable_patchRoutesOnNavigation` ([#11970](https://github.com/remix-run/react-router/pull/11970))
+## 6.28.1
 
 ### Patch Changes
 
-- No changes ([`506329c4e`](https://github.com/remix-run/react-router/commit/506329c4e2e7aba9837cbfa44df6103b49423745))
-
-- chore: re-enable development warnings through a `development` exports condition. ([#12269](https://github.com/remix-run/react-router/pull/12269))
-
-- Remove unstable upload handler. ([#12015](https://github.com/remix-run/react-router/pull/12015))
-
-- Remove unneeded dependency on @web3-storage/multipart-parser ([#12274](https://github.com/remix-run/react-router/pull/12274))
-
-- Fix redirects returned from loaders/actions using `data()` ([#12021](https://github.com/remix-run/react-router/pull/12021))
-
-- fix(react-router): (v7) fix static prerender of non-ascii characters ([#12161](https://github.com/remix-run/react-router/pull/12161))
-
-- Replace `substr` with `substring` ([#12080](https://github.com/remix-run/react-router/pull/12080))
-
-- Remove the deprecated `json` utility ([#12146](https://github.com/remix-run/react-router/pull/12146))
-
-  - You can use [`Response.json`](https://developer.mozilla.org/en-US/docs/Web/API/Response/json_static) if you still need to construct JSON responses in your app
-
-- Remove unneeded dependency on source-map ([#12275](https://github.com/remix-run/react-router/pull/12275))
+- Allow users to opt out of deprecation warnings by setting flags to false ([#12441](https://github.com/remix-run/react-router/pull/12441))
 
 ## 6.28.0
 
 ### Minor Changes
 
-- - Log deprecation warnings for v7 flags ([#11750](https://github.com/remix-run/react-router/pull/11750))
+- Log deprecation warnings for v7 flags ([#11750](https://github.com/remix-run/react-router/pull/11750))
   - Add deprecation warnings to `json`/`defer` in favor of returning raw objects
     - These methods will be removed in React Router v7