fix(deps): update dependency react-router-dom to v5.3.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-router-dom	5.0.1 -> 5.3.4

---

Release Notes

remix-run/react-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

• Fix: make v5 Router compatible with v18 StrictMode by @​jgoz in https://github.com/remix-run/react-router/pull/8831

v5.3.1

Compare Source

This release adds missing LICENSE files to the published build.

v5.3.0

Compare Source

This release of react-router-dom adds support for passing a function to either the className or style props to conditionally apply values based on the link's active state.

This provides similar functionality as the existing activeClassName and activeStyle props, but is a bit more powerful. For example, you can now easily apply styles exclusively to an inactive NavLink as well. This offers a nicer experience for folks who use utility class-based CSS tools such as Tailwind.

function Comp() {
  return (
    <NavLink
      to="/"
      className={isActive =>
        `px-3 py-2 ${isActive ? 'text-gray-200' : 'text-gray-800'}`
      }
    >
      Home
    </NavLink>
  );
}

Note that as of v6.0.0-beta.3, the activeClassName and activeStyle props are removed completely. Adding support for functional className and style props to both v5 and v6 will give v5 users an easier upgrade path.

Thanks to @​tim-phillips for raising the issue that inspired the change! 🥳

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

• Add sensitive prop on NavLink (#​7251 by @​caseywebdev)
• Fix Link component prop type check (#​7276 by @​ypyakymiv)
• Update mini-create-react-context (#​7288 by @​patricksmms)
• Separate history to its own context (#​7103 by @​illuminist)

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)

---

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.