Skip to content
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.

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

[Snyk] Upgrade react-router-dom from 5.2.0 to 5.3.0 #164

Closed

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Oct 5, 2021

Snyk has created this PR to upgrade react-router-dom from 5.2.0 to 5.3.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released a month ago, on 2021-09-03.
Release notes
Package name: react-router-dom
  • 5.3.0 - 2021-09-03

    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! 🥳

  • 5.2.1 - 2021-08-27

    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 #5362 for details. 🥳

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

  • 5.2.0 - 2020-05-11

    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

from react-router-dom GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@kevinxh
Copy link
Collaborator

kevinxh commented Oct 7, 2021

closing since this change is manually done in #168

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

Successfully merging this pull request may close these issues.

2 participants