Update dependency react-router to v5.2.0 #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mend-for-github-com[bot]](https://avatars.githubusercontent.com/in/30796?s=60&v=4){kind=small}
mend-for-github-com
bot
changed the title
mend-for-github-com
bot
deleted the
whitesource-remediate/react-router-5.x
branch
mend-for-github-com
bot
changed the title
mend-for-github-com
bot
restored the
whitesource-remediate/react-router-5.x
branch
mend-for-github-com
bot
force-pushed
the
whitesource-remediate/react-router-5.x
branch
from
40c2af6 to
244b603
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
5.1.2->5.2.0By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
remix-run/react-router (react-router)
v5.2.0Compare 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'scomponentprop and support asensitiveprop on NavLink for control over case sensitive matching.Enjoy!
Changes
sensitiveprop on NavLink (#7251 by @caseywebdev)componentprop type check (#7276 by @ypyakymiv)mini-create-react-context(#7288 by @patricksmms)historyto its own context (#7103 by @illuminist)