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]

Minor Changes

• Add nonce prop to Links & PrefetchPageLinks (#14048)
• Add loaderData arguments/properties alongside existing data arguments/properties to provide consistency and clarity between loaderData and actionData across the board (#14047)
  • Updated types: Route.MetaArgs, Route.MetaMatch, MetaArgs, MetaMatch, Route.ComponentProps.matches, UIMatch
  • @deprecated warnings have been added to the existing data properties to point users to new loaderData properties, in preparation for removing the data properties in a future major release

Patch Changes

• [UNSTABLE] Ensure resource route errors go through handleError w/middleware enabled (#14078)

• [REMOVE] Few additional fixes for returning/throwing data from middleware - attach to Handle middlewares returning responses without calling next #14093 (#14128)

• Prevent "Did not find corresponding fetcher result" console error when navigating during a fetcher.submit revalidation (#14114)

• Bubble client-side middleware errors prior to next to the appropriate ancestor error boundary (#14138)

• Switch Lazy Route Discovery manifest URL generation to usea standalone URLSearchParams instance instead of URL.searchParams to avoid a major performance bottleneck in Chrome (#14084)

• [UNSTABLE] Propagate returned Response from server middleware if next wasn't called (#14093)

• [UNSTABLE] Allow server middlewares to return data() values which will be converted into a Response (#14093)

• [UNSTABLE] Update middleware error handling so that the next function never throws and instead handles any middleware errors at the proper ErrorBoundary and returns the Response up through the ancestor next function (#14118)

• • [UNSTABLE] When middleware is enabled, make the context parameter read-only (via Readonly<unstable_RouterContextProvider>) so that TypeScript will not allow you to write arbitrary fields to it in loaders, actions, or middleware. (#14097)

• [UNSTABLE] Rename and alter the signature/functionality of the unstable_respond API in staticHandler.query/staticHandler.queryRoute (#14103)

  • The API has been renamed to unstable_generateMiddlewareResponse for clarity
  • The main functional change is that instead of running the loaders/actions before calling unstable_respond and handing you the result, we now pass a query/queryRoute function as a parameter and you execute the loaders/actions inside your callback, giving you full access to pre-processing and error handling
  • The query version of the API now has a signature of (query: (r: Request) => Promise<StaticHandlerContext | Response>) => Promise<Response>
  • The queryRoute version of the API now has a signature of (queryRoute: (r: Request) => Promise<Response>) => Promise<Response>
  • This allows for more advanced usages such as running logic before/after calling query and direct error handling of errors thrown from query
  • ⚠️ This is a breaking change if you've adopted the staticHandler unstable_respond API

  let response = await staticHandler.query(request, {
    requestContext: new unstable_RouterContextProvider(),
    async unstable_generateMiddlewareResponse(query) {
      try {
        // At this point we've run middleware top-down so we need to call the
        // handlers and generate the Response to bubble back up the middleware
        let result = await query(request);
        if (isResponse(result)) {
          return result; // Redirects, etc.
        }
        return await generateHtmlResponse(result);
      } catch (error: unknown) {
        return generateErrorResponse(error);
      }
    },
  });

• [UNSTABLE] Convert internal middleware implementations to use the new unstable_generateMiddlewareResponse API (#14103)

• Adjust internal RSC usage of React.use to avoid Webpack compilation errors when using React 18 (#14113)

• [UNSTABLE] Change getLoadContext signature (type GetLoadContextFunction) when future.unstable_middleware is enabled so that it returns an unstable_RouterContextProvider instance instead of a Map used to contruct the instance internally (#14097)

  • This also removes the type unstable_InitialContext export
  • ⚠️ This is a breaking change if you have adopted middleware and are using a custom server with a getLoadContext function

• Remove dependency on @types/node in TypeScript declaration files (#14059)

• Fix types for UIMatch to reflect that the loaderData/data properties may be undefined (#12206)

  • When an ErrorBoundary is being rendered, not all active matches will have loader data available, since it may have been their loader that threw to trigger the boundary
  • The UIMatch.data type was not correctly handing this and would always reflect the presence of data, leading to the unexpected runtime errors when an ErrorBoundary was rendered
  • ⚠️ This may cause some type errors to show up in your code for unguarded match.data accesses - you should properly guard for undefined values in those scenarios.

  // app/root.tsx
  export function loader() {
    someFunctionThatThrows(); // ❌ Throws an Error
    return { title: "My Title" };
  }
  
  export function Layout({ children }: { children: React.ReactNode }) {
    let matches = useMatches();
    let rootMatch = matches[0] as UIMatch<Awaited<ReturnType<typeof loader>>>;
    //  ^ rootMatch.data is incorrectly typed here, so TypeScript does not
    //    complain if you do the following which throws an error at runtime:
    let { title } = rootMatch.data; // 💥
  
    return <html>...</html>;
  }

• [UNSTABLE] Run client middleware on client navigations even if no loaders exist (#14106)

• [UNSTABLE] Change the unstable_getContext signature on RouterProvider/HydratedRouter/unstable_RSCHydratedRouter so that it returns an unstable_RouterContextProvider instance instead of a Map used to contruct the instance internally (#14097)

  • ⚠️ This is a breaking change if you have adopted the unstable_getContext prop

• proxy server action side-effect redirects from actions for document and callServer requests (#14131)

• Fix RSC Data Mode issue where routes that return false from shouldRevalidate would be replaced by an <Outlet /> (#14071)

@react-router/[email protected]

Patch Changes

• [UNSTABLE] Change getLoadContext signature (type GetLoadContextFunction) when future.unstable_middleware is enabled so that it returns an unstable_RouterContextProvider instance instead of a Map used to contruct the instance internally (#14097)

  • This also removes the type unstable_InitialContext export
  • ⚠️ This is a breaking change if you have adopted middleware and are using a custom server with a getLoadContext function

• Updated dependencies:

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

@react-router/[email protected]

Patch Changes

• [UNSTABLE] Change getLoadContext signature (type GetLoadContextFunction) when future.unstable_middleware is enabled so that it returns an unstable_RouterContextProvider instance instead of a Map used to contruct the instance internally (#14097)

  • This also removes the type unstable_InitialContext export
  • ⚠️ This is a breaking change if you have adopted middleware and are using a custom server with a getLoadContext function

• Updated dependencies:

  • [email protected]

@react-router/[email protected]

Patch Changes

• Fix rename without mkdir in Vite plugin (#14105)
• Updated dependencies:
  • [email protected]
  • @react-router/[email protected]
  • @react-router/[email protected]

[email protected]

Patch Changes

• Updated dependencies:
  • [email protected]

@react-router/[email protected]

Patch Changes

• [UNSTABLE] Change getLoadContext signature (type GetLoadContextFunction) when future.unstable_middleware is enabled so that it returns an unstable_RouterContextProvider instance instead of a Map used to contruct the instance internally (#14097)

  • This also removes the type unstable_InitialContext export
  • ⚠️ This is a breaking change if you have adopted middleware and are using a custom server with a getLoadContext function

• Updated dependencies:

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

@react-router/[email protected]

Patch Changes

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

@react-router/[email protected]

Patch Changes

• [UNSTABLE] Change getLoadContext signature (type GetLoadContextFunction) when future.unstable_middleware is enabled so that it returns an unstable_RouterContextProvider instance instead of a Map used to contruct the instance internally (#14097)

  • This also removes the type unstable_InitialContext export
  • ⚠️ This is a breaking change if you have adopted middleware and are using a custom server with a getLoadContext function

• Updated dependencies:

  • [email protected]

@react-router/[email protected]

Patch Changes

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

@react-router/[email protected]

Patch Changes

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

[email protected]