[Snyk] Upgrade react-router-dom from 5.2.0 to 5.3.0 #164
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade react-router-dom from 5.2.0 to 5.3.0.
ℹ️ 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.
Release notes
Package name: react-router-dom
This release of
react-router-dom
adds support for passing a function to either theclassName
orstyle
props to conditionally apply values based on the link'sactive
state.This provides similar functionality as the existing
activeClassName
andactiveStyle
props, but is a bit more powerful. For example, you can now easily apply styles exclusively to an inactiveNavLink
as well. This offers a nicer experience for folks who use utility class-based CSS tools such as Tailwind.Note that as of
v6.0.0-beta.3
, theactiveClassName
andactiveStyle
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! 🥳
This release fixes a bug with
<Link>
so that, when theto
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!
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
'scomponent
prop and support asensitive
prop on NavLink for control over case sensitive matching.Enjoy!
Changes
sensitive
prop on NavLink (#7251 by @ caseywebdev)component
prop type check (#7276 by @ ypyakymiv)mini-create-react-context
(#7288 by @ patricksmms)history
to its own context (#7103 by @ illuminist)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