Update react-router monorepo to v6.17.0 (dynamicSdk) - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router	6.15.0 -> 6.17.0
react-router-dom	6.15.0 -> 6.17.0

---

Release Notes

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

v6.17.0

Compare Source

Patch Changes

• Fix RouterProvider future prop type to be a Partial<FutureConfig> so that not all flags must be specified (#​10900)
• Updated dependencies:
  • @remix-run/router@1.10.0

v6.16.0

Compare Source

Minor Changes

• In order to move towards stricter TypeScript support in the future, we're aiming to replace current usages of any with unknown on exposed typings for user-provided data. To do this in Remix v2 without introducing breaking changes in React Router v6, we have added generics to a number of shared types. These continue to default to any in React Router and are overridden with unknown in Remix. In React Router v7 we plan to move these to unknown as a breaking change. (#​10843)
  • Location now accepts a generic for the location.state value
  • ActionFunctionArgs/ActionFunction/LoaderFunctionArgs/LoaderFunction now accept a generic for the context parameter (only used in SSR usages via createStaticHandler)
  • The return type of useMatches (now exported as UIMatch) accepts generics for match.data and match.handle - both of which were already set to unknown
• Move the @private class export ErrorResponse to an UNSAFE_ErrorResponseImpl export since it is an implementation detail and there should be no construction of ErrorResponse instances in userland. This frees us up to export a type ErrorResponse which correlates to an instance of the class via InstanceType. Userland code should only ever be using ErrorResponse as a type and should be type-narrowing via isRouteErrorResponse. (#​10811)
• Export ShouldRevalidateFunctionArgs interface (#​10797)
• Removed private/internal APIs only required for the Remix v1 backwards compatibility layer and no longer needed in Remix v2 (_isFetchActionRedirect, _hasFetcherDoneAnything) (#​10715)

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.9.0

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

v6.17.0

Compare Source

Minor Changes

• Add experimental support for the View Transitions API via document.startViewTransition to enable CSS animated transitions on SPA navigations in your application. (#​10916)

  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) {
    let 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 with React Router, check out our fork of the 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.

  Please note, that because the ViewTransition API is a DOM API, we now export a specific RouterProvider from react-router-dom with this functionality. If you are importing RouterProvider from react-router, then it will not support view transitions. (#​10928

Patch Changes

• Log a warning and fail gracefully in ScrollRestoration when sessionStorage is unavailable (#​10848)
• Updated dependencies:
  • @remix-run/router@1.10.0
  • react-router@6.17.0

v6.16.0

Compare Source

Minor Changes

• Updated dependencies:
  • @remix-run/router@1.9.0
  • react-router@6.16.0

Patch Changes

• Properly encode rendered URIs in server rendering to avoid hydration errors (#​10769)

---

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
b2c-retail-sample-app	✅ Ready (Inspect)	Visit Preview	Nov 17, 2023 6:17am