fix(deps): update dependency react-router-dom to v6

This MR contains the following updates:

Package	Type	Update	Change
react-router-dom	dependencies	major	^5.2.0 -> ^6.0.0

• update react router to v6
• removes bottomBar component in favor of css

Maybe change redirection mechanism ? https://gist.github.com/mjackson/b5748add2795ce7448a366ae8f8ae3bb#handling-redirects-in-react-router-v6

---

Release Notes

remix-run/react-router

v6.15.0

Compare Source

Minor Changes

• Add's a new redirectDocument() function which allows users to specify that a redirect from a loader/action should trigger a document reload (via window.location) instead of attempting to navigate to the redirected location via React Router (#​10705)

Patch Changes

• Fixes an edge-case affecting web extensions in Firefox that use URLSearchParams and the useSearchParams hook. (#​10620)
• Do not include hash in useFormAction() for unspecified actions since it cannot be determined on the server and causes hydration issues (#​10758)
• Reorder effects in unstable_usePrompt to avoid throwing an exception if the prompt is unblocked and a navigation is performed synchronously (#​10687, #​10718)
• Updated dependencies:
  • @remix-run/router@1.8.0
  • react-router@6.15.0

v6.14.2

Compare Source

Patch Changes

• Properly decode element id when emulating hash scrolling via <ScrollRestoration> (#​10682)
• Add missing <Form state> prop to populate history.state on submission navigations (#​10630)
• Support proper hydration of Error subclasses such as ReferenceError/TypeError (#​10633)
• Updated dependencies:
  • @remix-run/router@1.7.2
  • react-router@6.14.2

v6.14.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@6.14.1
  • @remix-run/router@1.7.1

v6.14.0

Compare Source

Minor Changes

• Add support for application/json and text/plain encodings for useSubmit/fetcher.submit. To reflect these additional types, useNavigation/useFetcher now also contain navigation.json/navigation.text and fetcher.json/fetcher.text which include the json/text submission if applicable (#​10413)

  // The default behavior will still serialize as FormData
  function Component() {
    let navigation = useNavigation();
    let submit = useSubmit();
    submit({ key: "value" }, { method: "post" });
    // navigation.formEncType => "application/x-www-form-urlencoded"
    // navigation.formData    => FormData instance
  }
  
  async function action({ request }) {
    // request.headers.get("Content-Type") => "application/x-www-form-urlencoded"
    // await request.formData()            => FormData instance
  }

  // Opt-into JSON encoding with `encType: "application/json"`
  function Component() {
    let navigation = useNavigation();
    let submit = useSubmit();
    submit({ key: "value" }, { method: "post", encType: "application/json" });
    // navigation.formEncType => "application/json"
    // navigation.json        => { key: "value" }
  }
  
  async function action({ request }) {
    // request.headers.get("Content-Type") => "application/json"
    // await request.json()                => { key: "value" }
  }

  // Opt-into text encoding with `encType: "text/plain"`
  function Component() {
    let navigation = useNavigation();
    let submit = useSubmit();
    submit("Text submission", { method: "post", encType: "text/plain" });
    // navigation.formEncType => "text/plain"
    // navigation.text        => "Text submission"
  }
  
  async function action({ request }) {
    // request.headers.get("Content-Type") => "text/plain"
    // await request.text()                => "Text submission"
  }

Patch Changes

• When submitting a form from a submitter element, prefer the built-in new FormData(form, submitter) instead of the previous manual approach in modern browsers (those that support the new submitter parameter) (#​9865, #​10627)
  • For browsers that don't support it, we continue to just append the submit button's entry to the end, and we also add rudimentary support for type="image" buttons
  • If developers want full spec-compliant support for legacy browsers, they can use the formdata-submitter-polyfill
• Call window.history.pushState/replaceState before updating React Router state (instead of after) so that window.location matches useLocation during synchronous React 17 rendering (#​10448)
  • ️ However, generally apps should not be relying on window.location and should always reference useLocation when possible, as window.location will not be in sync 100% of the time (due to popstate events, concurrent mode, etc.)
• Fix tsc --skipLibCheck:false issues on React 17 (#​10622)
• Upgrade typescript to 5.1 (#​10581)
• Updated dependencies:
  • react-router@6.14.0
  • @remix-run/router@1.7.0

v6.13.0

Compare Source

Minor Changes

• Move React.startTransition usage behind a future flag to avoid issues with existing incompatible Suspense usages. We recommend folks adopting this flag to be better compatible with React concurrent mode, but if you run into issues you can continue without the use of startTransition until v7. Issues usually boils down to creating net-new promises during the render cycle, so if you run into issues you should either lift your promise creation out of the render cycle or put it behind a useMemo. (#​10596)

  Existing behavior will no longer include React.startTransition:

  <BrowserRouter>
    <Routes>{/*...*/}</Routes>
  </BrowserRouter>
  
  <RouterProvider router={router} />

  If you wish to enable React.startTransition, pass the future flag to your component:

  <BrowserRouter future={{ v7_startTransition: true }}>
    <Routes>{/*...*/}</Routes>
  </BrowserRouter>
  
  <RouterProvider router={router} future={{ v7_startTransition: true }}/>

Patch Changes

• Work around webpack/terser React.startTransition minification bug in production mode (#​10588)
• Updated dependencies:
  • react-router@6.13.0

v6.12.1

Compare Source

Warning Please use version 6.13.0 or later instead of 6.12.1. This version suffers from a webpack/terser minification issue resulting in invalid minified code in your resulting production bundles which can cause issues in your application. See #​10579 for more details.

Patch Changes

• Adjust feature detection of React.startTransition to fix webpack + react 17 compilation error (#​10569)
• Updated dependencies:
  • react-router@6.12.1

v6.12.0

Compare Source

Minor Changes

• Wrap internal router state updates with React.startTransition if it exists (#​10438)

Patch Changes

• Re-throw DOMException (DataCloneError) when attempting to perform a PUSH navigation with non-serializable state. (#​10427)
• Updated dependencies:
  • @remix-run/router@1.6.3
  • react-router@6.12.0

v6.11.2

Compare Source

Patch Changes

• Export SetURLSearchParams type (#​10444)
• Updated dependencies:
  • react-router@6.11.2
  • @remix-run/router@1.6.2

v6.11.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@6.11.1
  • @remix-run/router@1.6.1

v6.11.0

Compare Source

Minor Changes

• Enable basename support in useFetcher (#​10336)
  • If you were previously working around this issue by manually prepending the basename then you will need to remove the manually prepended basename from your fetcher calls (fetcher.load('/basename/route') -> fetcher.load('/route'))

Patch Changes

• Fix inadvertent re-renders when using Component instead of element on a route definition (#​10287)
• Fail gracefully on <Link to="//"> and other invalid URL values (#​10367)
• Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#​10377, #​10409)
• Add static prop to StaticRouterProvider's internal Router component (#​10401)
• When using a RouterProvider, useNavigate/useSubmit/fetcher.submit are now stable across location changes, since we can handle relative routing via the @remix-run/router instance and get rid of our dependence on useLocation(). When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation(). (#​10336)
• Updated dependencies:
  • react-router@6.11.0
  • @remix-run/router@1.6.0

v6.10.0

Compare Source

Minor Changes

• Added support for Future Flags in React Router. The first flag being introduced is future.v7_normalizeFormMethod which will normalize the exposed useNavigation()/useFetcher() formMethod fields as uppercase HTTP methods to align with the fetch() behavior. (#​10207)

  • When future.v7_normalizeFormMethod === false (default v6 behavior),
    • useNavigation().formMethod is lowercase
    • useFetcher().formMethod is lowercase
  • When future.v7_normalizeFormMethod === true:
    • useNavigation().formMethod is uppercase
    • useFetcher().formMethod is uppercase

Patch Changes

• Fix createStaticHandler to also check for ErrorBoundary on routes in addition to errorElement (#​10190)
• Updated dependencies:
  • @remix-run/router@1.5.0
  • react-router@6.10.0

v6.9.0

Compare Source

Minor Changes

• React Router now supports an alternative way to define your route element and errorElement fields as React Components instead of React Elements. You can instead pass a React Component to the new Component and ErrorBoundary fields if you choose. There is no functional difference between the two, so use whichever approach you prefer . You shouldn't be defining both, but if you do Component/ErrorBoundary will "win". (#​10045)

  Example JSON Syntax

  // Both of these work the same:
  const elementRoutes = [{
    path: '/',
    element: <Home />,
    errorElement: <HomeError />,
  }]
  
  const componentRoutes = [{
    path: '/',
    Component: Home,
    ErrorBoundary: HomeError,
  }]
  
  function Home() { ... }
  function HomeError() { ... }

  Example JSX Syntax

  // Both of these work the same:
  const elementRoutes = createRoutesFromElements(
    <Route path='/' element={<Home />} errorElement={<HomeError /> } />
  );
  
  const componentRoutes = createRoutesFromElements(
    <Route path='/' Component={Home} ErrorBoundary={HomeError} />
  );
  
  function Home() { ... }
  function HomeError() { ... }

• Introducing Lazy Route Modules! (#​10045)

  In order to keep your application bundles small and support code-splitting of your routes, we've introduced a new lazy() route property. This is an async function that resolves the non-route-matching portions of your route definition (loader, action, element/Component, errorElement/ErrorBoundary, shouldRevalidate, handle).

  Lazy routes are resolved on initial load and during the loading or submitting phase of a navigation or fetcher call. You cannot lazily define route-matching properties (path, index, children) since we only execute your lazy route functions after we've matched known routes.

  Your lazy functions will typically return the result of a dynamic import.

  // In this example, we assume most folks land on the homepage so we include that
  // in our critical-path bundle, but then we lazily load modules for /a and /b so
  // they don't load until the user navigates to those routes
  let routes = createRoutesFromElements(
    <Route path="/" element={<Layout />}>
      <Route index element={<Home />} />
      <Route path="a" lazy={() => import("./a")} />
      <Route path="b" lazy={() => import("./b")} />
    </Route>
  );

  Then in your lazy route modules, export the properties you want defined for the route:

  export async function loader({ request }) {
    let data = await fetchData(request);
    return json(data);
  }
  
  // Export a `Component` directly instead of needing to create a React Element from it
  export function Component() {
    let data = useLoaderData();
  
    return (
      <>
        <h1>You made it!</h1>
        <p>{data}</p>
      </>
    );
  }
  
  // Export an `ErrorBoundary` directly instead of needing to create a React Element from it
  export function ErrorBoundary() {
    let error = useRouteError();
    return isRouteErrorResponse(error) ? (
      <h1>
        {error.status} {error.statusText}
      </h1>
    ) : (
      <h1>{error.message || error}</h1>
    );
  }

  An example of this in action can be found in the examples/lazy-loading-router-provider directory of the repository.

  Huge thanks to @​rossipedia for the Initial Proposal and POC Implementation.

• Updated dependencies:

  • react-router@6.9.0
  • @remix-run/router@1.4.0

v6.8.2

Compare Source

Patch Changes

• Treat same-origin absolute URLs in <Link to> as external if they are outside of the router basename (#​10135)
• Fix useBlocker to return IDLE_BLOCKER during SSR (#​10046)
• Fix SSR of absolute <Link to> urls (#​10112)
• Properly escape HTML characters in StaticRouterProvider serialized hydration data (#​10068)
• Updated dependencies:
  • @remix-run/router@1.3.3
  • react-router@6.8.2

v6.8.1

Compare Source

Patch Changes

• Improved absolute url detection in Link component (now also supports mailto: urls) (#​9994)
• Fix partial object (search or hash only) pathnames losing current path value (#​10029)
• Updated dependencies:
  • react-router@6.8.1
  • @remix-run/router@1.3.2

v6.8.0

Compare Source

Minor Changes

• Support absolute URLs in <Link to>. If the URL is for the current origin, it will still do a client-side navigation. If the URL is for a different origin then it will do a fresh document request for the new origin. (#​9900)

  <Link to="https://neworigin.com/some/path">    {/* Document request */}
  <Link to="//neworigin.com/some/path">          {/* Document request */}
  <Link to="https://www.currentorigin.com/path"> {/* Client-side navigation */}

Patch Changes

• Fix bug with search params removal via useSearchParams (#​9969)
• Respect preventScrollReset on <fetcher.Form> (#​9963)
• Fix navigation for hash routers on manual URL changes (#​9980)
• Use pagehide instead of beforeunload for <ScrollRestoration>. This has better cross-browser support, specifically on Mobile Safari. (#​9945)
• Updated dependencies:
  • @remix-run/router@1.3.1
  • react-router@6.8.0

v6.7.0

Compare Source

Minor Changes

• Add unstable_useBlocker hook for blocking navigations within the app's location origin (#​9709)
• Add unstable_usePrompt hook for blocking navigations within the app's location origin (#​9932)
• Add preventScrollReset prop to <Form> (#​9886)

Patch Changes

• Added pass-through event listener options argument to useBeforeUnload (#​9709)
• Streamline jsdom bug workaround in tests (#​9824)
• Updated dependencies:
  • @remix-run/router@1.3.0
  • react-router@6.7.0

v6.6.2

Compare Source

Patch Changes

• Ensure useId consistency during SSR (#​9805)
• Updated dependencies:
  • react-router@6.6.2

v6.6.1

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.2.1
  • react-router@6.6.1

v6.6.0

Compare Source

Minor Changes

• Add useBeforeUnload() hook (#​9664)
• Remove unstable_ prefix from createStaticHandler/createStaticRouter/StaticRouterProvider (#​9738)

Patch Changes

• Proper hydration of Error objects from StaticRouterProvider (#​9664)
• Support uppercase <Form method> and useSubmit method values (#​9664)
• Skip initial scroll restoration for SSR apps with hydrationData (#​9664)
• Fix <button formmethod> form submission overriddes (#​9664)
• Updated dependencies:
  • @remix-run/router@1.2.0
  • react-router@6.6.0

v6.5.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@6.5.0
  • @remix-run/router@1.1.0

v6.4.5

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/router@1.0.5
  • react-router@6.4.5

v6.4.4

Compare Source

Patch Changes

• Fix issues with encoded characters in NavLink and descendant <Routes> (#​9589, #​9647)
• Properly serialize/deserialize ErrorResponse instances when using built-in hydration (#​9593)
• Support basename in static data routers (#​9591)
• Updated dependencies:
  • @remix-run/router@1.0.4
  • react-router@6.4.4

v6.4.3

Compare Source

Patch Changes

• Fix hrefs generated for createHashRouter (#​9409)
• fix encoding/matching issues with special chars (#​9477, #​9496)
• Properly support index routes with a path in useResolvedPath (#​9486)
• Respect relative=path prop on NavLink (#​9453)
• Fix NavLink behavior for root urls (#​9497)
• Updated dependencies:
  • @remix-run/router@1.0.3
  • react-router@6.4.3

v6.4.2

Compare Source

Patch Changes

• Respect basename in useFormAction (#​9352)
• Enhance console error messages for invalid usage of data router hooks (#​9311)
• If an index route has children, it will result in a runtime error. We have strengthened our RouteObject/RouteProps types to surface the error in TypeScript. (#​9366)
• Updated dependencies:
  • react-router@6.4.2
  • @remix-run/router@1.0.2

v6.4.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@6.4.1
  • @remix-run/router@1.0.1

v6.4.0

Compare Source

Whoa this is a big one! 6.4.0 brings all the data loading and mutation APIs over from Remix. Here's a quick high level overview, but it's recommended you go check out the docs, especially the feature overview and the tutorial.

New APIs

• Create your router with createMemoryRouter/createBrowserRouter/createHashRouter
• Render your router with <RouterProvider>
• Load data with a Route loader and mutate with a Route action
• Handle errors with Route errorElement
• Submit data with the new <Form> component
• Perform in-page data loads and mutations with useFetcher()
• Defer non-critical data with defer and Await
• Manage scroll position with <ScrollRestoration>

New Features

• Perform path-relative navigations with <Link relative="path"> (#​9160)

Bug Fixes

• Path resolution is now trailing slash agnostic (#​8861)
• useLocation returns the scoped location inside a <Routes location> component (#​9094)
• respect the <Link replace> prop if it is defined (#​8779)

Updated Dependencies

• react-router@6.4.0

v6.3.0

Compare Source

What's Changed

• Added the v5 to v6 backwards compatibility package (https://github.com/remix-run/react-router/pull/8752). The official guide can be found in this discussion

New Contributors

• @​mfijas made their first contribution in https://github.com/remix-run/react-router/pull/8717
• @​ThornWu made their first contribution in https://github.com/remix-run/react-router/pull/8718
• @​janpaepke made their first contribution in https://github.com/remix-run/react-router/pull/8651
• @​rtmann made their first contribution in https://github.com/remix-run/react-router/pull/8725

Full Changelog: https://github.com/remix-run/react-router/compare/v6.2.2...v6.3.0

v6.2.2

Compare Source

What's Changed

Bug Fixes

• Fixed nested splat routes that begin with special URL-safe characters (#​8563)
• Fixed a bug where index routes were missing route context in some cases (#​8497)

New Contributors

• @​chasinhues made their first contribution in https://github.com/remix-run/react-router/pull/8514
• @​underager made their first contribution in https://github.com/remix-run/react-router/pull/8531
• @​kantuni made their first contribution in https://github.com/remix-run/react-router/pull/8537
• @​ArjaanBuijk made their first contribution in https://github.com/remix-run/react-router/pull/8536
• @​jmargeta made their first contribution in https://github.com/remix-run/react-router/pull/8548
• @​koojaa made their first contribution in https://github.com/remix-run/react-router/pull/8542
• @​chrisngobanh made their first contribution in https://github.com/remix-run/react-router/pull/8576
• @​ChristopherChudzicki made their first contribution in https://github.com/remix-run/react-router/pull/8582
• @​awreese made their first contribution in https://github.com/remix-run/react-router/pull/8596
• @​bhbs made their first contribution in https://github.com/remix-run/react-router/pull/8601
• @​LukerSpringtree made their first contribution in https://github.com/remix-run/react-router/pull/8619
• @​hsbtr made their first contribution in https://github.com/remix-run/react-router/pull/8476
• @​abhi-kr-2100 made their first contribution in https://github.com/remix-run/react-router/pull/8658
• @​cvbuelow made their first contribution in https://github.com/remix-run/react-router/pull/8663
• @​hyesungoh made their first contribution in https://github.com/remix-run/react-router/pull/8666
• @​BrianT1414 made their first contribution in https://github.com/remix-run/react-router/pull/8667
• @​IbraRouisDev made their first contribution in https://github.com/remix-run/react-router/pull/8683
• @​shihanng made their first contribution in https://github.com/remix-run/react-router/pull/8689
• @​latin-1 made their first contribution in https://github.com/remix-run/react-router/pull/8529
• @​Isammoc made their first contribution in https://github.com/remix-run/react-router/pull/8533
• @​KutnerUri made their first contribution in https://github.com/remix-run/react-router/pull/8278
• @​shamsup made their first contribution in https://github.com/remix-run/react-router/pull/8563
• @​brophdawg11 made their first contribution in https://github.com/remix-run/react-router/pull/8691

Full Changelog: https://github.com/remix-run/react-router/compare/v6.2.1...v6.2.2

v6.2.1

Compare Source

This release updates the internal history dependency to 5.2.0.

Full Changelog: https://github.com/remix-run/react-router/compare/v6.2.0...v6.2.1

v6.2.0

Compare Source

Bug fixes

• Fixed the RouteProps element type, which should be a ReactNode (#​8473)
• Fixed a bug with useOutlet for top-level routes (#​8483)

Features

• We now use statically analyzable CJS exports. This enables named imports in Node ESM scripts (See the commit).

New Contributors

• @​thisiskartik made their first contribution in https://github.com/remix-run/react-router/pull/8487
• @​vijaypushkin made their first contribution in https://github.com/remix-run/react-router/pull/8491

Full Changelog: https://github.com/remix-run/react-router/compare/v6.1.1...v6.2.0

v6.1.1

Compare Source

In v6.1.0 we inadvertently shipped a new, undocumented API that will likely introduce bugs (#​7586). We have flagged HistoryRouter as unstable_HistoryRouter, as this API will likely need to change before a new major release.

Full Changelog: https://github.com/remix-run/react-router/compare/v6.1.0...v6.1.1

v6.1.0

Compare Source

Bug fixes

• Fixed a bug that broke support for base64 encoded IDs on nested routes (#​8291)

Features

• <Outlet> can now receive a context prop. This value is passed to child routes and is accessible via the new useOutletContext hook. See the API docs for details. (#​8461)
• <NavLink> can now receive a child function for access to its props. (#​8164)

Enhancements

• Improved TypeScript signature for useMatch and matchPath. For example, when you call useMatch("foo/:bar/:baz"), the path is parsed and the return type will be PathMatch<"bar" | "baz">. (#​8030)
• A few error message improvements (#​8202)

New Contributors

• @​rwieruch made their first contribution in https://github.com/remix-run/react-router/pull/8244
• @​codeiotic made their first contribution in https://github.com/remix-run/react-router/pull/8247
• @​Sannnao made their first contribution in https://github.com/remix-run/react-router/pull/8263
• @​mattmazzola made their first contribution in https://github.com/remix-run/react-router/pull/8255
• @​ngokevin made their first contribution in https://github.com/remix-run/react-router/pull/8267
• @​TimisRobert made their first contribution in https://github.com/remix-run/react-router/pull/8269
• @​mikeldking made their first contribution in https://github.com/remix-run/react-router/pull/8279
• @​fishmandev made their first contribution in https://github.com/remix-run/react-router/pull/8289
• @​rjerue made their first contribution in https://github.com/remix-run/react-router/pull/8304
• @​rockingskier made their first contribution in https://github.com/remix-run/react-router/pull/8314
• @​arinthros made their first contribution in https://github.com/remix-run/react-router/pull/8337
• @​noisypigeon made their first contribution in https://github.com/remix-run/react-router/pull/8361
• @​elylucas made their first contribution in https://github.com/remix-run/react-router/pull/8368
• @​paulsmithkc made their first contribution in https://github.com/remix-run/react-router/pull/8357
• @​sanketshah19 made their first contribution in https://github.com/remix-run/react-router/pull/8372
• @​JakubDrozd made their first contribution in https://github.com/remix-run/react-router/pull/8402
• @​markivancho made their first contribution in https://github.com/remix-run/react-router/pull/8414
• @​turansky made their first contribution in https://github.com/remix-run/react-router/pull/8420
• @​shivamsinghchahar made their first contribution in https://github.com/remix-run/react-router/pull/8423
• @​petersendidit made their first contribution in https://github.com/remix-run/react-router/pull/8436
• @​Ajayff4 made their first contribution in https://github.com/remix-run/react-router/pull/8373
• @​RobHannay made their first contribution in https://github.com/remix-run/react-router/pull/8455
• @​kddnewton made their first contribution in https://github.com/remix-run/react-router/pull/8030
• @​brockross made their first contribution in https://github.com/remix-run/react-router/pull/8462
• @​sergiodxa made their first contribution in https://github.com/remix-run/react-router/pull/8164
• @​baozouai made their first contribution in https://github.com/remix-run/react-router/pull/8171
• @​liuhanqu made their first contribution in https://github.com/remix-run/react-router/pull/8374

Full Changelog: https://github.com/remix-run/react-router/compare/v6.0.1...v6.1.0

v6.0.2

Compare Source

Features

• Added the reloadDocument prop to <Link>. This allows <Link> to function like a normal anchor tag by reloading the document after navigation while maintaining the relative to resolution.

️ Docs

• Fixed several issues in docblocks and the docs themselves. See the full changelog for the deets!

New Contributors

• @​rwieruch made their first contribution in https://github.com/remix-run/react-router/pull/8244
• @​ProProgrammer2504 made their first contribution in https://github.com/remix-run/react-router/pull/8247
• @​Sannnao made their first contribution in https://github.com/remix-run/react-router/pull/8263
• @​mattmazzola made their first contribution in https://github.com/remix-run/react-router/pull/8255
• @​ngokevin made their first contribution in https://github.com/remix-run/react-router/pull/8267
• @​TimisRobert made their first contribution in https://github.com/remix-run/react-router/pull/8269
• @​mikeldking made their first contribution in https://github.com/remix-run/react-router/pull/8279
• @​fishmandev made their first contribution in https://github.com/remix-run/react-router/pull/8289

Full Changelog

v6.0.1

Compare Source

Bug Fixes

• Add a default <StaticRouter location> value (#​8243)
• Add invariant for using <Route> inside <Routes> to help people make the change (#​8238)

v6.0.0

Compare Source

React Router v6 is here!

Please go read our blog post for more information on all the great stuff in v6 including notes about how to upgrade from React Router v5 and Reach Router.

v5.3.4

Compare Source

We removed the mini-create-react-context dependency, moving it into an internal module to eliminate peer dependency warnings for users on React 18 (#​9382).

Full Changelog: https://github.com/remix-run/react-router/compare/v5.3.3...v5.3.4

---

Configuration

Schedule: At any time (no schedule defined).

Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, click this checkbox.

---

This MR has been generated by Renovate Bot.