Bump react-router-dom from 5.2.0 to 5.3.0

[dependabot]

Bumps react-router-dom from 5.2.0 to 5.3.0.

Release notes

Sourced from react-router-dom's releases.

v5.3.0

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

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 remix-run/react-router#5362 for details. 🥳

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

Commits

• 7a89146 v5.3.0
• b3c7d99 NavLink: Add support for className and style props as functions (#7983)
• cc61615 update release script
• b483747 add publish script
• 23191e1 temp: remove release action
• 92dcd15 v5.2.1
• 953af40 start publish and version scripts
• 4092300 Update lerna
• 80b6ffa Replace state on repeated Link navigations (#7864)
• df9d7d4 Replace NPM with Yarn in quick start guide (#7966)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by chancestrickland, a new releaser for react-router-dom since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)