Update dependency react-router-dom to v6 #64
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.2.0
->^6.0.0
By merging this PR, the issue #63 will be automatically resolved and closed:
Release Notes
remix-run/react-router (react-router-dom)
v6.0.0
Compare Source
React Router v6 is here!
Please go read our blog post for more information on all the great stuff in v6 including notes about how to upgrade from React Router v5 and Reach 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
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 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! 🥳
v5.2.1
Compare Source
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 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!