-
Notifications
You must be signed in to change notification settings - Fork 352
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
fix(deps): update dependency react-router-dom to v6 #3604
Conversation
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: site/package-lock.json
|
📊 Benchmark resultsComparing with 9165fe3 Package size: 363 MB⬇️ 0.00% decrease vs. 9165fe3
Legend
|
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 6.x releases. However, if you upgrade to 6.x manually then Renovate will reenable minor and patch updates automatically. If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
This PR contains the following updates:
^4.3.1
->^6.0.0
Release Notes
remix-run/react-router
v6.0.1
Compare Source
🐛 Bug Fixes
<StaticRouter location>
value (#8243)<Route>
inside<Routes>
to help people make the change (#8238)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.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!
v5.2.0
Compare 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
'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)v5.1.2
Compare Source
List of commits
Bugfixes
<Link ref>
error on React 15 (#6954)v5.1.1
Compare Source
List of commits
Bugfixes
v5.1.0
Compare Source
Read the blog post
List of commits
Features
useParams
,useLocation
,useHistory
, anduseRouteMatch
hooks (d6224d6
)forwardRef
in<Link>
(b5528ed
)<Link to>
and<NavLink to>
(#5331, #5368)<Link component>
API (#5437)Bugfixes
<Route children>
elements when the<Route>
does not match (9665659
)v5.0.1
Compare Source
Changes
Updates
10d78bb
)10d78bb
)992af48
)Bugfixes
6a99c93
)017f692
and2ce1d32
)f9849c8
, then992af48
)3ccbd19
)7bd1407
)82ce94c
)56c829b
)a38ef04
)caa9950
)Thanks to @StringEpsilon for putting this list together. Enjoy!
v5.0.0
Compare Source
Note: While this does have a major version bump, it is actually a minor release. We screwed up some of the dependency version selection in 4.3.1, which necessitated a major bump. See this blog post for details.
Please ensure you have upgraded both
react-router
andreact-router-dom
(react-router-native
for RN users) to the exact same version. If different versions of those two packages are in your application, you will get errors when using<Link>
and otherreact-router-dom
-specific components. You can ensure you have the correct versions of both packages in your app usingnpm ls react-router react-router-dom
.Breaking Changes
withRouter()
or a<Route/>
instead.Refactor as follows:
b2c6fa0
), i.E. combining CJS imports with ESM imports.New Features
<Route />
now supports an array of paths - #5889 (thanks @baronswindle)Full Changelog
<Route />
now supports multiple child nodes when using react >= 16.0.componentWillMount
andcomponentWillReceiveProps
<StrictMode/>
<Link />
not working properly with target="_self" - #6138 (thanks @ericyang89)eval
in development to be compliant with unsafe-eval CSP - #6611babel-preset-env
Configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.