Skip to content

Update dependency react-router to v6 #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency react-router to v6 #36

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link

@renovate renovate bot commented Oct 19, 2021 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-router ^2.0.0 -> ^6.0.0 age adoption passing confidence

Release Notes

remix-run/react-router

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:

Patch Changes
  • Fix generatePath incorrectly applying parameters in some cases (#​10078)
  • Improve memoization for context providers to avoid unnecessary re-renders (#​9983)

v6.8.2

Compare Source

Patch Changes

v6.8.1

Compare Source

Patch Changes
  • Remove inaccurate console warning for POP navigations and update active blocker logic (#​10030)
  • Updated dependencies:

v6.8.0

Compare Source

Patch Changes

v6.7.0

Compare Source

Minor Changes
  • Add unstable_useBlocker hook for blocking navigations within the app's location origin (#​9709)
Patch Changes
  • Fix generatePath when optional params are present (#​9764)
  • Update <Await> to accept ReactNode as children function return result (#​9896)
  • Updated dependencies:

v6.6.2

Compare Source

Patch Changes
  • Ensure useId consistency during SSR (#​9805)

v6.6.1

Compare Source

Patch Changes

v6.6.0

Compare Source

Patch Changes

v6.5.0

Compare Source

This release introduces support for Optional Route Segments. Now, adding a ? to the end of any path segment will make that entire segment optional. This works for both static segments and dynamic parameters.

Optional Params Examples

  • <Route path=":lang?/about> will match:
    • /:lang/about
    • /about
  • <Route path="/multistep/:widget1?/widget2?/widget3?"> will match:
    • /multistep
    • /multistep/:widget1
    • /multistep/:widget1/:widget2
    • /multistep/:widget1/:widget2/:widget3

Optional Static Segment Example

  • <Route path="/home?"> will match:
    • /
    • /home
  • <Route path="/fr?/about"> will match:
    • /about
    • /fr/about
Minor Changes
  • Allows optional routes and optional static segments (#​9650)
Patch Changes
  • Stop incorrectly matching on partial named parameters, i.e. <Route path="prefix-:param">, to align with how splat parameters work. If you were previously relying on this behavior then it's recommended to extract the static portion of the path at the useParams call site: (#​9506)
// Old behavior at URL /prefix-123
<Route path="prefix-:id" element={<Comp /> }>

function Comp() {
  let params = useParams(); // { id: '123' }
  let id = params.id; // "123"
  ...
}

// New behavior at URL /prefix-123
<Route path=":id" element={<Comp /> }>

function Comp() {
  let params = useParams(); // { id: 'prefix-123' }
  let id = params.id.replace(/^prefix-/, ''); // "123"
  ...
}

v6.4.5

Compare Source

Patch Changes

v6.4.4

Compare Source

Patch Changes

v6.4.3

Compare Source

Patch Changes
  • useRoutes should be able to return null when passing locationArg (#​9485)
  • fix initialEntries type in createMemoryRouter (#​9498)
  • Updated dependencies:

v6.4.2

Compare Source

Patch Changes
  • Fix IndexRouteObject and NonIndexRouteObject types to make hasErrorElement optional (#​9394)
  • 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:

v6.4.1

Compare Source

Patch Changes

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
  • Render your router with <RouterProvider>
  • Load data with a Route loader and mutate with a Route action
  • Handle errors with Route errorElement
  • Defer non-critical data with defer and Await

Bug Fixes

  • Path resolution is now trailing slash agnostic (#​8861)
  • useLocation returns the scoped location inside a <Routes location> component (#​9094)

Updated Dependencies

v6.3.0: [email protected]

Compare Source

What's Changed

New Contributors

Full Changelog: remix-run/react-router@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

Full Changelog: remix-run/react-router@v6.2.1...v6.2.2

v6.2.1

Compare Source

This release updates the internal history dependency to 5.2.0.

Full Changelog: remix-run/react-router@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

Full Changelog: remix-run/react-router@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: remix-run/react-router@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

Full Changelog: remix-run/react-router@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

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: remix-run/react-router@v5.3.3...v5.3.4

v5.3.3

Compare Source

This release fixes a bad version selector in react-router-native.

v5.3.2

Compare Source

v5.3.1

Compare Source

This release adds missing LICENSE files to the published build.

v5.2.1

Compare Source

This release fixes a bug with <Link> so that, when the to location is the same as the current, the history state entry is replaced instead of pushed to the stack. See https://github.com/remix-run/react-router/issues/5362 for details. 🥳

Thanks to @​guidobouman for the PR and for everyone else who weighed in for the fix!

v5.2.0

Compare Source

This release includes a notable performance boost by separating the "Router" context from the "History" context internally. We also allow every element type for Link's component prop and support a sensitive prop on NavLink for control over case sensitive matching.

Enjoy!

Changes

v5.1.2

Compare Source

List of commits
Bugfixes
  • Fix lingering <Link ref> error on React 15 (#​6954)

v5.1.1

Compare Source

List of commits
Bugfixes
  • Fix issue with useParams reading from null object (#​6940)
  • Fix regression passing ref to functional components in React <= 16.2 (#​6934)
  • Fix regression passing empty string to matchPath (#​6941)

v5.1.0

Compare Source

Read the blog post
List of commits
Features
  • Add useParams, useLocation, useHistory, and useRouteMatch hooks (d6224d6)
  • Add support for forwardRef in <Link> (b5528ed)
  • Add support for functions in <Link to> and <NavLink to> (#​5331, #​5368)
  • Add <Link component> API (#​5437)
Bugfixes
  • Don't render <Route children> elements when the <Route> does not match (9665659)

v5.0.1

Compare Source

Changes
Updates
  • Reduced component depth in withRouter() HOC. (10d78bb)
  • Changed misleading warning when withRouter is used outside a Router (10d78bb)
  • Reduced install size and bundle size by switching to mini-create-react-context (992af48)
Bugfixes
  • Fixed display name for router context consumer and provider (6a99c93)
  • Fixed infinite loop caused by Redirect in some scenarios (017f692 and 2ce1d32)
  • Fixed license issue for react context polyfill (f9849c8, then 992af48)
  • Fixed Redirect throwing an exception in StaticRouter without context (3ccbd19)
  • Fixed regression in matchPath that caused an exception for empty paths (7bd1407)
  • Fixed page reload when an exception was thrown in Link onClick (82ce94c)
  • Fixed warning about createRef or useRef values in wrappedComponentRef when using withRouter() (56c829b)
  • Fixed withRouter() wrapped component inside NavLink not working properly (a38ef04)
  • Fixed CJS build - previously, incorrect exports were emitted (caa9950)

Thanks to @​StringEpsilon for putting this list together. Enjoy!

v5.0.0

Compare Source

Note: While this does have a major version bump, it is actually a minor release. We screwed up some of the dependency version selection in 4.3.1, which necessitated a major bump. See this blog post for details.
⚠️ Upgrade Warning ⚠️

Please ensure you have upgraded both react-router and react-router-dom (react-router-native for RN users) to the exact same version. If different versions of those two packages are in your application, you will get errors when using <Link> and other react-router-dom-specific components. You can ensure you have the correct versions of both packages in your app using npm ls react-router react-router-dom.

Breaking Changes

  • Since the old context API is no longer used, any access to the old context will fail. Use of the react router context is not supported, please use withRouter() or a <Route/> instead.
  • Due to the new context API, mixing of imports will now result in an exception:
// Be careful, this won't work anymore!
import BrowserRouter from 'react-router-dom/BrowserRouter';
import { Route } from 'react-router-dom';

<BrowserRouter>
  <Route />
</BrowserRouter>

Refactor as follows:

// These are both from the same build and use the same context object
// so there won't be a mismatch :)
import { BrowserRouter, Route } from 'react-router-dom';
  • In development mode, we now throw an error when using 2 different builds (see b2c6fa0), i.E. combining CJS imports with ESM imports.

New Features

<Route path={["/BigApple", "/NYC", "NewYork"]} component={NewYork} />

Full Changelog

  • <Route /> now supports multiple child nodes when using react >= 16.0.
  • Migrated to new react context API, with a polyfill for react versions < 16.2
  • Removed deprecated lifecycle methods componentWillMount and componentWillReceiveProps
  • Introduced more warnings in development builds
  • Changed build-process to rollup:
    • Smaller build size
    • Package now includes pre-minified files
    • Package now consists of single-file builds that include all modules.
  • Upgraded to history 4.9.0
  • Per file imports are deprecated and will be removed in a future major version. For now, a warning will be logged.
  • Made sure that react router conforms to react <StrictMode/>
  • Fixed <Link /> not working properly with target="_self" - #​6138 (thanks @​ericyang89)
  • Fixed prop-type warning when using forwardRef - #​6417 (thanks @​frehner and @​eXon)
  • Added support for createRef in - #​6567 (thanks @​gcangussu)
  • Removed use of eval in development to be compliant with unsafe-eval CSP - #​6611
  • Migrated to babel-preset-env
  • Improved testing infrastructure to improve developer workflow
  • Several docs improvements - #​6410 (thanks @​justsml)

v4.3.1

Compare Source

Just a patch to fix an accidental move of warning from a normal dependency to a devDependency, which was causing issues with installation.

v4.3.0

Compare Source

The major new things of this release are Redirect with params (see #​5209) and the new generatePath API. We also cleaned up the code with Prettier, so browsing through it should be more enjoyable.

One other thing to mention, while I have your attention, is the deprecation of react-router-redux. It's no longer maintained and has a number of fundamental problems (particularly around time travel). Integrating Redux and the DOM History API is challenging because they don't maintain the same semantics and the resulting integration is error prone. Getting to the router context will be easier in future versions of React Router, so the main motivations for needing it will be going away. So, while I would advise against trying to integrate the two, for those that still want this functionality can turn to libraries like @​supasate's connected-react-router.

Changes

v4.2.0

Aug 23, 2017

v4.1.1

Compare Source

Apr 12, 2017

  • Fixes for the various PropTypes related issues.

Note: This work is still ongoing, as the React team still has some outstanding issues to figure out themselves. Keep an eye on this issue and the prop-types repo for updates as we all work through this craziness.

v4.1.0

Compare Source

Apr 11, 2017

  • Add wrappedComponent to the component returned by withRouter
  • Add wrappedComponentRef prop to the component returned by withRouter
  • Add non-react static methods and properties of the wrapped component to the component returned by withRouter

v4.0.0

Compare Source

Mar 10, 2017

  • Released! No code changes from 4.0.0-beta.8

v3.2.6

Compare Source

v3.2.5

Compare Source

v3.2.4

Compare Source

v3.2.3

Compare Source

This release includes the missing UMD build from the 3.2.2. Sorry about that!

v3.2.2

Compare Source

v3.2.1

Compare Source

  • React 16.3 support

v3.2.0

Compare Source

  • React 16 support

v3.0.5

Compare Source

  • Manually set displayName for components
  • Async hooks could be removed during simultaneous server requests (#​4941 by @​s-yadav)

v3.0.4

Compare Source

  • Fixes for React 15.5 deprecation warnings

v3.0.3

Compare Source

v3.0.2

Compare Source

  • Re-add module entry to package.json

v3.0.1

Compare Source

v3.0.0

Compare Source

🎉 The 100th release of React Router! 🎉

This release removes all the deprecation warnings from v2.x along with some bugfixes.

While the focus of this project is shifting towards the component-based v4, this branch will be maintained indefinitely!

Bug fixes will continue to be accepted. We are not going to leave anyone hanging and want to assure you that v3 development will be alive and well.

Changes

Oct 24, 2016

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-react-router-monorepo branch from a575dd2 to c3a1ec3 Compare March 7, 2022 15:00
@renovate renovate bot changed the title Update dependency react-router to v5 Update dependency react-router to v6 Mar 7, 2022
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023 •
edited
Loading

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@renovate-bot