fix(deps): update dependency react-router-native to ^6.30.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-router-native (source)	^6.16.0 -> ^6.30.0

---

Release Notes

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

v6.30.0

Compare Source

Date: 2025-02-27

Minor Changes

• Add fetcherKey as a parameter to patchRoutesOnNavigation (#​13109)

Patch Changes

• Fix regression introduced in 6.29.0 via #​12169 that caused issues navigating to hash routes inside splat routes for applications using Lazy Route Discovery (patchRoutesOnNavigation) (#​13108)

Full Changelog: v6.29.0...v6.30.0

v6.29.0

Compare Source

Date: 2025-01-30

Minor Changes

• Provide the request signal as a parameter to patchRoutesOnNavigation (#​12900)
  • This can be used to abort any manifest fetches if the in-flight navigation/fetcher is aborted

Patch Changes

• Do not log v7 deprecation warnings in production builds (#​12794)
• Properly bubble headers when throwing a data() result (#​12845)
• Optimize route matching by skipping redundant matchRoutes calls when possible (#​12169)
• Strip search parameters from patchRoutesOnNavigation path param for fetcher calls (#​12899)

Full Changelog: v6.28.2...v6.29.0

v6.28.2

Compare Source

Date: 2025-01-16

Patch Changes

• Fix manual fetcher key usage when not opted into future.v7_fetcherPersist (#​12674)
• Fix issue with fetcher data cleanup in the data layer on fetcher unmount (#​12674)

Full Changelog: v6.28.1...v6.28.2

v6.28.1

Compare Source

Date: 2024-12-20

Patch Changes

• Allow users to opt out of v7 deprecation warnings by setting flags to false (#​12441)

Full Changelog: v6.28.0...v6.28.1

v6.28.0

Compare Source

Date: 2024-11-06

What's Changed

• In preparation for v7 we've added deprecation warnings for any future flags that you have not yet opted into. Please use the flags to better prepare for eventually upgrading to v7.

Minor Changes

• Log deprecation warnings for v7 flags (#​11750)
  • Add deprecation warnings to json/defer in favor of returning raw objects
    • These methods will be removed in React Router v7

Patch Changes

• Update JSDoc URLs for new website structure (add /v6/ segment) (#​12141)

Full Changelog: v6.27.0...v6.28.0

v6.27.0

Compare Source

Date: 2024-10-11

What's Changed

Stabilized APIs

This release stabilizes a handful of "unstable" APIs in preparation for the pending React Router v7 release (see these posts for more info):

• unstable_dataStrategy → dataStrategy (createBrowserRouter and friends) (Docs)
• unstable_patchRoutesOnNavigation → patchRoutesOnNavigation (createBrowserRouter and friends) (Docs)
• unstable_flushSync → flushSync (useSubmit, fetcher.load, fetcher.submit) (Docs)
• unstable_viewTransition → viewTransition (<Link>, <Form>, useNavigate, useSubmit) (Docs)

Minor Changes

• Stabilize the unstable_flushSync option for navigations and fetchers (#​11989)
• Stabilize the unstable_viewTransition option for navigations and the corresponding unstable_useViewTransitionState hook (#​11989)
• Stabilize unstable_dataStrategy (#​11974)
• Stabilize unstable_patchRoutesOnNavigation (#​11973)
  • Add new PatchRoutesOnNavigationFunctionArgs type for convenience (#​11967)

Patch Changes

• Fix bug when submitting to the current contextual route (parent route with an index child) when an ?index param already exists from a prior submission (#​12003)
• Fix useFormAction bug - when removing ?index param it would not keep other non-Remix index params (#​12003)
• Fix bug with fetchers not persisting preventScrollReset through redirects during concurrent fetches (#​11999)
• Avoid unnecessary console.error on fetcher abort due to back-to-back revalidation calls (#​12050)
• Fix bugs with partialHydration when hydrating with errors (#​12070)
• Remove internal cache to fix issues with interrupted patchRoutesOnNavigation calls (#​12055)
  • ⚠️ This may be a breaking change if you were relying on this behavior in the unstable_ API
  • We used to cache in-progress calls to patchRoutesOnNavigation internally so that multiple navigations with the same start/end would only execute the function once and use the same promise
  • However, this approach was at odds with patch short circuiting if a navigation was interrupted (and the request.signal aborted) since the first invocation's patch would no-op
  • This cache also made some assumptions as to what a valid cache key might be - and is oblivious to any other application-state changes that may have occurred
  • So, the cache has been removed because in most cases, repeated calls to something like import() for async routes will already be cached automatically - and if not it's easy enough for users to implement this cache in userland
• Remove internal discoveredRoutes FIFO queue from unstable_patchRoutesOnNavigation (#​11977)
  • ⚠️ This may be a breaking change if you were relying on this behavior in the unstable_ API
  • This was originally implemented as an optimization but it proved to be a bit too limiting
  • If you need this optimization you can implement your own cache inside patchRoutesOnNavigation
• Fix types for RouteObject within PatchRoutesOnNavigationFunction's patch method so it doesn't expect agnostic route objects passed to patch (#​11967)
• Expose errors thrown from patchRoutesOnNavigation directly to useRouteError instead of wrapping them in a 400 ErrorResponse instance (#​12111)

Full Changelog: v6.26.2...v6.27.0

v6.26.2

Compare Source

Date: 2024-09-09

Patch Changes

• Update the unstable_dataStrategy API to allow for more advanced implementations (#​11943)
  • ⚠️ If you have already adopted unstable_dataStrategy, please review carefully as this includes breaking changes to this API
  • Rename unstable_HandlerResult to unstable_DataStrategyResult
  • Change the return signature of unstable_dataStrategy from a parallel array of unstable_DataStrategyResult[] (parallel to matches) to a key/value object of routeId => unstable_DataStrategyResult
    • This allows more advanced control over revalidation behavior because you can opt-into or out-of revalidating data that may not have been revalidated by default (via match.shouldLoad)
  • You should now return/throw a result from your handlerOverride instead of returning a DataStrategyResult
    • The return value (or thrown error) from your handlerOverride will be wrapped up into a DataStrategyResult and returned fromm match.resolve
    • Therefore, if you are aggregating the results of match.resolve() into a final results object you should not need to think about the DataStrategyResult type
    • If you are manually filling your results object from within your handlerOverride, then you will need to assign a DataStrategyResult as the value so React Router knows if it's a successful execution or an error (see examples in the documentation for details)
  • Added a new fetcherKey parameter to unstable_dataStrategy to allow differentiation from navigational and fetcher calls
• Preserve opted-in view transitions through redirects (#​11925)
• Preserve pending view transitions through a router revalidation call (#​11917)
• Fix blocker usage when blocker.proceed is called quickly/synchronously (#​11930)

Full Changelog: v6.26.1...v6.26.2

v6.26.1

Compare Source

Date: 2024-08-15

Patch Changes

• Rename unstable_patchRoutesOnMiss to unstable_patchRoutesOnNavigation to match new behavior (#​11888)
• Update unstable_patchRoutesOnNavigation logic so that we call the method when we match routes with dynamic param or splat segments in case there exists a higher-scoring static route that we've not yet discovered (#​11883)
  • We also now leverage an internal FIFO queue of previous paths we've already called unstable_patchRoutesOnNavigation against so that we don't re-call on subsequent navigations to the same path

Full Changelog: v6.26.0...v6.26.1

v6.26.0

Compare Source

Date: 2024-08-01

Minor Changes

• Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#​11811)
• Add a new unstable_data() API for usage with Remix Single Fetch (#​11836)
  • This API is not intended for direct usage in React Router SPA applications
  • It is primarily intended for usage with createStaticHandler.query() to allow loaders/actions to return arbitrary data along with custom status/headers without forcing the serialization of data into a Response instance
  • This allows for more advanced serialization tactics via unstable_dataStrategy such as serializing via turbo-stream in Remix Single Fetch
  • ⚠️ This removes the status field from HandlerResult
    • If you need to return a specific status from unstable_dataStrategy you should instead do so via unstable_data()

Patch Changes

• Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations (#​11839)
• Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#​11838)
  • During initial hydration, router.state.matches will now include any partial matches so that we can render ancestor HydrateFallback components

Full Changelog: v6.25.1...v6.26.0

v6.25.1

Compare Source

Date: 2024-07-17

Patch Changes

• Memoize some RouterProvider internals to reduce unnecessary re-renders (#​11803)

Full Changelog: v6.25.0...v6.25.1

v6.25.0

Compare Source

Date: 2024-07-16

What's Changed

Stabilized v7_skipActionErrorRevalidation

This release stabilizes the future.unstable_skipActionErrorRevalidation flag into future.v7_skipActionErrorRevalidation in preparation for the upcoming React Router v7 release.

• When this flag is enabled, actions that return/throw a 4xx/5xx Response will not trigger a revalidation by default
• This also stabilizes shouldRevalidate's unstable_actionStatus parameter to actionStatus

Minor Changes

• Stabilize future.unstable_skipActionErrorRevalidation as future.v7_skipActionErrorRevalidation (#​11769)

Patch Changes

• Fix regression and properly decode paths inside useMatch so matches/params reflect decoded params (#​11789)
• Fix bubbling of errors thrown from unstable_patchRoutesOnMiss (#​11786)
• Fix hydration in SSR apps using unstable_patchRoutesOnMiss that matched a splat route on the server (#​11790)

Full Changelog: v6.24.1...v6.25.0

v6.24.1

Compare Source

Date: 2024-07-03

Patch Changes

• Remove polyfill.io reference from warning message because the domain was sold and has since been determined to serve malware (#​11741)
  • See https://sansec.io/research/polyfill-supply-chain-attack
• Export NavLinkRenderProps type for easier typing of custom NavLink callback (#​11553)
• When using future.v7_relativeSplatPath, properly resolve relative paths in splat routes that are children of pathless routes (#​11633)
• Fog of War (unstable): Trigger a new router.routes identity/reflow during route patching (#​11740)
• Fog of War (unstable): Fix initial matching when a splat route matches (#​11759)

Full Changelog: v6.24.0...v6.24.1

v6.24.0

Compare Source

Date: 2024-06-24

What's Changed

Lazy Route Discovery (a.k.a. "Fog of War")

We're really excited to release our new API for "Lazy Route Discovery" in v6.24.0! For some background information, please check out the original RFC. The tl;dr; is that ever since we introduced the Data APIs in v6.4 via <RouterProvider>, we've been a little bummed that one of the tradeoffs was the lack of a compelling code-splitting story mirroring what we had in the <BrowserRouter>/<Routes> apps. We took a baby-step towards improving that story with route.lazy in v6.9.0, but with v6.24.0 we've gone the rest of the way.

With "Fog of War", you can now load portions of the route tree lazily via the new unstable_patchRoutesOnMiss option passed to createBrowserRouter (and it's memory/hash counterparts). This gives you a way to hook into spots where React Router is unable to match a given path and patch new routes into the route tree during the navigation (or fetcher call).

Here's a very small example, but please refer to the documentation for more information and use cases:

const router = createBrowserRouter(
  [
    {
      id: "root",
      path: "/",
      Component: RootComponent,
    },
  ],
  {
    async unstable_patchRoutesOnMiss({ path, patch }) {
      if (path === "/a") {
        // Load the `a` route (`{ path: 'a', Component: A }`)
        let route = await getARoute();
        // Patch the `a` route in as a new child of the `root` route
        patch("root", [route]);
      }
    },
  },
);

Minor Changes

• Add support for Lazy Route Discovery (a.k.a. "Fog of War") (#​11626)

Patch Changes

• Fix fetcher.submit types - remove incorrect navigate/fetcherKey/unstable_viewTransition options because they are only relevant for useSubmit (#​11631)
• Allow falsy location.state values passed to <StaticRouter> (#​11495)

Full Changelog: v6.23.1...v6.24.0

v6.23.1

Compare Source

Date: 2024-05-10

Patch Changes

• Allow undefined to be resolved through <Await> (#​11513)
• Add defensive document check when checking for document.startViewTransition availability (#​11544)
• Change the react-router-dom/server import back to react-router-dom instead of index.ts (#​11514)
• @remix-run/router - Support unstable_dataStrategy on staticHandler.queryRoute (#​11515)

Full Changelog: v6.23.0...v6.23.1

v6.23.0

Compare Source

Date: 2024-04-23

What's Changed

Data Strategy (unstable)

The new unstable_dataStrategy API is a low-level API designed for advanced use-cases where you need to take control over the data strategy for your loader/action functions. The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix "Single Fetch", user-land middleware/context APIs, automatic loader caching, and more. Please see the docs for more information.

Note: This is a low-level API intended for advanced use-cases. This overrides React Router's internal handling of loader/action execution, and if done incorrectly will break your app code. Please use with caution and perform the appropriate testing.

Skip Action Error Revalidation (unstable)

Currently, all active loader's revalidate after any action submission, regardless of the action result. However, in the majority of cases a 4xx/5xx response from an action means that no data was actually changed and the revalidation is unnecessary. We've introduced a new future.unstable_skipActionErrorRevalidation flag that changes the behavior here, and we plan to make this the default in future version of React Router.

With this flag enabled, action's that return/throw a 4xx/5xx response status will no longer automatically revalidate. If you need to revalidate after a 4xx/5xx result with this flag enabled, you can still do that via returning true from shouldRevalidate - which now also receives a new unstable_actionStatus argument alongside actionResult so you can make decision based on the status of the action response without having to encode it into the action data.

Minor Changes

• Add a new unstable_dataStrategy configuration option (#​11098, #​11377)
• @remix-run/router - Add a new future.unstable_skipActionRevalidation future flag (#​11098)
• @remix-run/router - SSR: Added a new skipLoaderErrorBubbling options to the staticHandler.query method to disable error bubbling by the static handler for use in Remix's Single Fetch implementation (#​11098, (#​11377))

Full Changelog: v6.22.3...v6.23.0

v6.22.3

Compare Source

Date: 2024-03-07

Patch Changes

• Fix a future.v7_partialHydration bug that would re-run loaders below the boundary on hydration if SSR loader errors bubbled to a parent boundary (#​11324)
• Fix a future.v7_partialHydration bug that would consider the router uninitialized if a route did not have a loader (#​11325)

Full Changelog: v6.22.2...v6.22.3

v6.22.2

Compare Source

Date: 2024-02-28

Patch Changes

• Preserve hydrated errors during partial hydration runs (#​11305)

Full Changelog: v6.22.1...v6.22.2

v6.22.1

Compare Source

Date: 2024-02-16

Patch Changes

• Fix encoding/decoding issues with pre-encoded dynamic parameter values (#​11199)

Full Changelog: v6.22.0...v6.22.1

v6.22.0

Compare Source

Date: 2024-02-01

What's Changed

Core Web Vitals Technology Report Flag

In 2021, the HTTP Archive launched the Core Web Vitals Technology Report dashboard:

By combining the powers of real-user experiences in the Chrome UX Report 26 (CrUX) dataset with web technology detections in HTTP Archive 30, we can get a glimpse into how architectural decisions like choices of CMS platform or JavaScript framework play a role in sites’ CWV performance.

They use a tool called wappalyzer to identify what technologies a given website is using by looking for certain scripts, global JS variables, or other identifying characteristics. For example, for Remix applications, they look for the global __remixContext variable to identify that a website is using Remix.

It was brought to our attention that React Router was unable to be reliably identified because there are no identifying global aspects. They are currently looking for external scripts with react-router in the name. This will identify sites using React Router from a CDN such as unpkg - but it will miss the vast majority of sites that are installing React Router from the npm registry and bundling it into their JS files. This results in drastically under-reporting the usage of React Router on the web.

Starting with version 6.22.0, sites using react-router-dom will begin adding a window.__reactRouterVersion variable that will be set to a string value of the SemVer major version number (i.e., window.__reactRouterVersion = "6";) so that they can be properly identified.

Minor Changes

• Include a window.__reactRouterVersion for CWV Report detection (#​11222)
• Add a createStaticHandler future.v7_throwAbortReason flag to throw request.signal.reason (defaults to a DOMException) when a request is aborted instead of an Error such as new Error("query() call aborted: GET /path") (#​11104)
  • Please note that DOMException was added in Node v17 so you will not get a DOMException on Node 16 and below.

Patch Changes

• Respect the ErrorResponse status code if passed to getStaticContextFormError (#​11213)

Full Changelog: v6.21.3...v6.22.0

v6.21.3

Compare Source

Date: 2024-01-18

Patch Changes

• Fix NavLink isPending when a basename is used (#​11195)
• Remove leftover unstable_ prefix from Blocker/BlockerFunction types (#​11187)

Full Changelog: v6.21.2...v6.21.3

v6.21.2

Compare Source

Date: 2024-01-11

Patch Changes

• Leverage useId for internal fetcher keys when available (#​11166)
• Fix bug where dashes were not picked up in dynamic parameter names (#​11160)
• Do not attempt to deserialize empty JSON responses (#​11164)

Full Changelog: v6.21.1...v6.21.2

v6.21.1

Compare Source

Date: 2023-12-21

Patch Changes

• Fix bug with route.lazy not working correctly on initial SPA load when v7_partialHydration is specified (#​11121)
• Fix bug preventing revalidation from occurring for persisted fetchers unmounted during the submitting phase (#​11102)
• De-dup relative path logic in resolveTo (#​11097)

Full Changelog: v6.21.0...v6.21.1

v6.21.0

Compare Source

Date: 2023-12-13

What's Changed

future.v7_relativeSplatPath

We fixed a splat route path-resolution bug in 6.19.0, but later determined a large number of applications were relying on the buggy behavior, so we reverted the fix in 6.20.1 (see #​10983, #​11052, #​11078).

The buggy behavior is that the default behavior when resolving relative paths inside a splat route would ignore any splat (*) portion of the current route path. When the future flag is enabled, splat portions are included in relative path logic within splat routes.

For more information, please refer to the useResolvedPath docs and/or the detailed changelog entry.

Partial Hydration

We added a new future.v7_partialHydration future flag for the @remix-run/router that enables partial hydration of a data router when Server-Side Rendering. This allows you to provide hydrationData.loaderData that has values for some initially matched route loaders, but not all. When this flag is enabled, the router will call loader functions for routes that do not have hydration loader data during router.initialize(), and it will render down to the deepest provided HydrateFallback (up to the first route without hydration data) while it executes the unhydrated routes. (#​11033)

Minor Changes

• Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#​11087)
• Add a new future.v7_partialHydration future flag that enables partial hydration of a data router when Server-Side Rendering (#​11033)

Patch Changes

• Properly handle falsy error values in ErrorBoundary's (#​11071)
• Catch and bubble errors thrown when trying to unwrap responses from loader/action functions (#​11061)
• Fix relative="path" issue when rendering Link/NavLink outside of matched routes (#​11062)

Full Changelog: v6.20.1...v6.21.0

v6.20.1

Compare Source

Date: 2023-12-01

Patch Changes

• Revert the useResolvedPath fix for splat routes due to a large number of applications that were relying on the buggy behavior (see #​11052) (#​11078)
  • We plan to re-introduce this fix behind a future flag in the next minor version (see this comment)
  • This fix was included in versions 6.19.0 and 6.20.0. If you are upgrading from 6.18.0 or earlier, you would not have been impacted by this fix.

Full Changelog: v6.20.0...v6.20.1

v6.20.0

Compare Source

Date: 2023-11-22

[!WARNING]
Please use version 6.20.1 or later instead of 6.20.0. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release (#​11045). We reverted the fix in 6.20.1 and will be re-introducing it behind a future flag in a subsequent release. See #​11052 for more details.

Minor Changes

• Export the PathParam type from the public API (#​10719)

Patch Changes

• Do not revalidate unmounted fetchers when v7_fetcherPersist is enabled (#​11044)
• Fix bug with resolveTo path resolution in splat routes (#​11045)
  • This is a follow up to #​10983 to handle the few other code paths using getPathContributingMatches
  • This removes the UNSAFE_getPathContributingMatches export from @remix-run/router since we no longer need this in the react-router/react-router-dom layers

Full Changelog: v6.19.0...v6.20.0

v6.19.0

Compare Source

Date: 2023-11-16

[!WARNING]
Please use version 6.20.1 or later instead of 6.19.0. We discovered that a large number of apps were relying on buggy behavior that was fixed in this release (#​10983). We reverted the fix in 6.20.1 and will be re-introducing it behind a future flag in a subsequent release. See #​11052 for more details.

What's Changed

unstable_flushSync API

This release brings a new unstable_flushSync option to the imperative APIs (useSubmit, useNavigate, fetcher.submit, fetcher.load) to let users opt-into synchronous DOM updates for pending/optimistic UI.

function handleClick() {
  submit(data, { flushSync: true });
  // Everything is flushed to the DOM so you can focus/scroll to your pending/optimistic UI
  setFocusAndOrScrollToNewlyAddedThing();
}

Minor Changes

• Add unstable_flushSync option to useNavigate/useSubmit/fetcher.load/fetcher.submit to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#​11005)
• Remove the unstable_ prefix from the useBlocker hook as it's been in use for enough time that we are confident in the API (#​10991)
  • We do not plan to remove the prefix from unstable_usePrompt due to differences in how browsers handle window.confirm that prevent React Router from guaranteeing consistent/correct behavior

Patch Changes

• Fix useActionData so it returns proper contextual action data and not any action data in the tree (#​11023)

• Fix bug in useResolvedPath that would cause useResolvedPath(".") in a splat route to lose the splat portion of the URL path. (#​10983)

  • ⚠️ This fixes a quite long-standing bug specifically for "." paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via "." inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.

• Fix issue where a changing fetcher key in a useFetcher that remains mounted wasn't getting picked up (#​11009)

• Fix useFormAction which was incorrectly inheriting the ?index query param from child route action submissions (#​11025)

• Fix NavLink active logic when to location has a trailing slash (#​10734)

• Fix types so unstable_usePrompt can accept a BlockerFunction in addition to a boolean (#​10991)

• Fix relative="path" bug where relative path calculations started from the full location pathname, instead of from the current contextual route pathname. (#​11006)

  <Route path="/a">
    <Route path="/b" element={<Component />}>
      <Route path="/c" />
    </Route>
  </Route>;
  
  function Component() {
    return (
      <>
        {/* This is now correctly relative to /a/b, not /a/b/c */}
        <Link to=".." relative="path" />
        <Outlet />
      </>
    );
  }

Full Changelog: 6.18.0...6.19.0

v6.18.0

Compare Source

Date: 2023-10-31

What's Changed

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors.

• You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
• Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
• Form and useSubmit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
  • <Form method="post" navigate={false} fetcherKey="my-key">
  • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })
  • Invoking a fetcher in this way is ephemeral and stateless
  • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

Persistence Future Flag (future.v7_fetcherPersist)

Per the same RFC as above, we've introduced a new future.v7_fetcherPersist flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an idle state. This makes pending/optimistic UI much easier in scenarios where the originating fetcher needs to unmount.

• This is sort of a long-standing bug fix as the useFetchers() API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an idle state
• Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:
  • Fetchers that complete while still mounted will no longer appear in useFetchers() after completion - they served no purpose in there since you can access the data via useFetcher().data
  • Fetchers that previously unmounted while in-flight will not be immediately aborted and will instead be cleaned up once they return to an idle state
    • They will remain exposed via useFetchers while in-flight so you can still access pending/optimistic data after unmount
    • If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI
    • However, if a fetcher was re-mounted elsewhere in the tree using the same key, then it's result will be processed, even if the originating fetcher was unmounted

Minor Changes

• Add fetcher key APIs and navigate=false options (#​10960)
• Add future.v7_fetcherPersist flag (#​10962)
• Add support for optional path segments in matchPath (#​10768)

Patch Changes

• Fix the future prop on BrowserRouter, HashRouter and MemoryRouter so that it accepts a Partial<FutureConfig> instead of requiring all flags to be included (#​10962)
• Fix router.getFetcher/router.deleteFetcher type definitions which incorrectly specified key as an optional parameter (#​10960)

Full Changelog: 6.17.0...6.18.0

v6.17.0

Compare Source

Date: 2023-10-16

What's Changed

View Transitions 🚀

We're excited to release experimental support for the View Transitions API in React Router! You can now trigger navigational DOM updates to be wrapped in document.startViewTransition to enable CSS animated transitions on SPA navigations in your application.

The simplest approach to enabling a View Transition in your React Router app is via the new <Link unstable_viewTransition> prop. This will cause the navigation DOM update to be wrapped in document.startViewTransition which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.

If you need to apply more fine-grained styles for your animations, you can leverage the unstable_useViewTransitionState hook which will tell you when a transition is in progress and you can use that to apply classes or styles:

function ImageLink(to, src, alt) {
  const isTransitioning = unstable_useViewTransitionState(to);
  return (
    <Link to={to} unstable_viewTransition>
      <img
        src={src}
        alt={alt}
        style={{
          viewTransitionName: isTransitioning ? "image-expand" : "",
        }}
      />
    </Link>
  );
}

You can also use the <NavLink unstable_viewTransition> shorthand which will manage the hook usage for you and automatically add a transitioning class to the <a> during the transition:

a.transitioning img {
  view-transition-name: "image-expand";
}

<NavLink to={to} unstable_viewTransition>
  <img src={src} alt={alt} />
</NavLink>

For an example usage of View Transitions, check out our fork of the awesome Astro Records demo.

For more information on using the View Transitions API, please refer to the Smooth and simple transitions with the View Transitions API guide from the Google Chrome team.

Minor Changes

• Add support for view transitions (#​10916)

Patch Changes

• Log a warning and fail gracefully in ScrollRestoration when sessionStorage is unavailable (#​10848)
• Fix RouterProvider future prop type to be a Partial<FutureConfig> so that not all flags must be specified (#​10900)
• Allow 404 detection to leverage root route error boundary if path contains a URL segment (#​10852)
• Fix ErrorResponse type to avoid leaking internal field (#​10876)

Full Changelog: 6.16.0...6.17.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.