This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
bump(deps): update dependency react-router-dom to ^6.26.2 #507
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/react-router-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
renovate
bot
requested review from
thedoublejay,
kyleleow and
pierregee
as code owners
October 31, 2023 17:49
github-actions
bot
added
the
kind/dependencies
Pull requests that update a dependency file
label
Oct 31, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 2, 2023 07:45
d535fea
to
f506298
Compare
renovate
bot
requested review from
chloezxyy,
fullstackninja864 and
lykalabrada
as code owners
November 2, 2023 07:45
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
3 times, most recently
from
November 13, 2023 13:38
7c256cb
to
5bb5490
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.18.0
bump(deps): update dependency react-router-dom to ^6.18.0 - autoclosed
Nov 14, 2023
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.18.0 - autoclosed
bump(deps): update dependency react-router-dom to ^6.18.0
Nov 16, 2023
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.18.0
bump(deps): update dependency react-router-dom to ^6.19.0
Nov 16, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 16, 2023 18:31
5bb5490
to
dcd10bb
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.19.0
bump(deps): update dependency react-router-dom to ^6.20.0
Nov 22, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 22, 2023 20:04
dcd10bb
to
2f42b8b
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.20.0
bump(deps): update dependency react-router-dom to ^6.20.1
Dec 1, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 1, 2023 20:01
2f42b8b
to
08ae268
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.20.1
bump(deps): update dependency react-router-dom to ^6.21.0
Dec 14, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 14, 2023 06:39
08ae268
to
2b79a7d
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.21.0
bump(deps): update dependency react-router-dom to ^6.21.1
Dec 21, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 21, 2023 19:16
2b79a7d
to
6e2fd48
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.21.1
bump(deps): update dependency react-router-dom to ^6.21.2
Jan 11, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
January 11, 2024 19:04
6e2fd48
to
a6a6a57
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.21.2
bump(deps): update dependency react-router-dom to ^6.21.3
Jan 18, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 1, 2024 22:38
64e36db
to
6d2dee1
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 16, 2024 22:45
6d2dee1
to
3b3f5b3
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.22.0
bump(deps): update dependency react-router-dom to ^6.22.1
Feb 16, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 28, 2024 21:44
3b3f5b3
to
676a278
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.22.1
bump(deps): update dependency react-router-dom to ^6.22.2
Feb 28, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 29, 2024 14:50
676a278
to
62e491e
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.22.2
bump(deps): update dependency react-router-dom to ^6.22.3
Mar 7, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
March 7, 2024 15:51
62e491e
to
15d6ed3
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
April 4, 2024 04:25
f120ea0
to
2a589d1
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
April 23, 2024 16:48
2a589d1
to
9820bdb
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.22.3
bump(deps): update dependency react-router-dom to ^6.23.0
Apr 23, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
May 10, 2024 20:12
9820bdb
to
30615e3
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.23.0
bump(deps): update dependency react-router-dom to ^6.23.1
May 10, 2024
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.23.1
bump(deps): update dependency react-router-dom to ^6.24.0
Jun 24, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 24, 2024 22:07
30615e3
to
d72295f
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
July 3, 2024 13:04
d72295f
to
3479d3e
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.24.0
bump(deps): update dependency react-router-dom to ^6.24.1
Jul 3, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
July 16, 2024 17:40
3479d3e
to
ac48c44
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.24.1
bump(deps): update dependency react-router-dom to ^6.25.0
Jul 16, 2024
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.25.0
bump(deps): update dependency react-router-dom to ^6.25.1
Jul 17, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
July 17, 2024 18:43
ac48c44
to
edee720
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
August 1, 2024 16:56
edee720
to
bd4c529
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.25.1
bump(deps): update dependency react-router-dom to ^6.26.0
Aug 1, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
August 15, 2024 16:34
bd4c529
to
cbd8054
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.26.0
bump(deps): update dependency react-router-dom to ^6.26.1
Aug 15, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
September 9, 2024 15:44
cbd8054
to
59e5504
Compare
renovate
bot
changed the title
bump(deps): update dependency react-router-dom to ^6.26.1
bump(deps): update dependency react-router-dom to ^6.26.2
Sep 9, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
^6.18.0
->^6.26.2
Release Notes
remix-run/react-router (react-router-dom)
v6.26.2
Compare Source
v6.26.1
Compare Source
v6.26.0
Compare Source
Minor Changes
replace(url, init?)
alternative toredirect(url, init?)
that performs ahistory.replaceState
instead of ahistory.pushState
on client-side navigation redirects (#11811)Patch Changes
future.v7_partialHydration
along withunstable_patchRoutesOnMiss
(#11838)router.state.matches
will now include any partial matches so that we can render ancestorHydrateFallback
components@remix-run/router@1.19.0
react-router@6.26.0
v6.25.1
Compare Source
Patch Changes
RouterProvider
internals to reduce unnecessary re-renders (#11803)react-router@6.25.1
v6.25.0
Compare Source
Minor Changes
Stabilize
future.unstable_skipActionErrorRevalidation
asfuture.v7_skipActionErrorRevalidation
(#11769)Response
with a4xx
/5xx
status codeshouldRevalidate
shouldRevalidate
'sunstable_actionStatus
parameter toactionStatus
Patch Changes
react-router@6.25.0
@remix-run/router@1.18.0
v6.24.1
Compare Source
Patch Changes
polyfill.io
reference from warning message because the domain was sold and has since been determined to serve malware (#11741)NavLinkRenderProps
type for easier typing of customNavLink
callback (#11553)@remix-run/router@1.17.1
react-router@6.24.1
v6.24.0
Compare Source
Minor Changes
Add support for Lazy Route Discovery (a.k.a. Fog of War) (#11626)
unstable_patchRoutesOnMiss
docs: https://reactrouter.com/en/main/routers/create-browser-routerPatch Changes
fetcher.submit
types - remove incorrectnavigate
/fetcherKey
/unstable_viewTransition
options because they are only relevant foruseSubmit
(#11631)location.state
values passed to<StaticRouter>
(#11495)react-router@6.24.0
@remix-run/router@1.17.0
v6.23.1
Compare Source
Patch Changes
document
existence when checkingstartViewTransition
(#11544)react-router-dom/server
import back toreact-router-dom
instead ofindex.ts
(#11514)@remix-run/router@1.16.1
react-router@6.23.1
v6.23.0
Compare Source
Minor Changes
unstable_dataStrategy
configuration option (#11098)Patch Changes
@remix-run/router@1.16.0
react-router@6.23.0
v6.22.3
Compare Source
Patch Changes
@remix-run/router@1.15.3
react-router@6.22.3
v6.22.2
Compare Source
Patch Changes
@remix-run/router@1.15.2
react-router@6.22.2
v6.22.1
Compare Source
v6.22.0
Compare Source
Minor Changes
window__reactRouterVersion
tag for CWV Report detection (#11222)Patch Changes
@remix-run/router@1.15.0
react-router@6.22.0
v6.21.3
Compare Source
Patch Changes
NavLink
isPending
when abasename
is used (#11195)unstable_
prefix fromBlocker
/BlockerFunction
types (#11187)react-router@6.21.3
v6.21.2
Compare Source
v6.21.1
Compare Source
Patch Changes
react-router@6.21.1
@remix-run/router@1.14.1
v6.21.0
Compare Source
Minor Changes
Add a new
future.v7_relativeSplatPath
flag to implement a breaking bug fix to relative routing when inside a splat route. (#11087)This fix was originally added in #10983 and was later reverted in #11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #11052)
The Bug
The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (
*
) portion of the current route path.The Background
This decision was originally made thinking that it would make the concept of nested different sections of your apps in
<Routes>
easier if relative routing would replace the current splat:Any paths like
/dashboard
,/dashboard/team
,/dashboard/projects
will match theDashboard
route. The dashboard component itself can then render nested<Routes>
:Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the
Dashboard
as its own independent app, or embed it into your large app without making any changes to it.The Problem
The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that
"."
always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using"."
:We've also introduced an issue that we can no longer move our
DashboardTeam
component around our route hierarchy easily - since it behaves differently if we're underneath a non-splat route, such as/dashboard/:widget
. Now, our"."
links will, properly point to ourself inclusive of the dynamic param value so behavior will break from it's corresponding usage in a/dashboard/*
route.Even worse, consider a nested splat route configuration:
Now, a
<Link to=".">
and a<Link to="..">
inside theDashboard
component go to the same place! That is definitely not correct!Another common issue arose in Data Routers (and Remix) where any
<Form>
should post to it's own routeaction
if you the user doesn't specify a form action:This is just a compounded issue from the above because the default location for a
Form
to submit to is itself ("."
) - and if we ignore the splat portion, that now resolves to the parent route.The Solution
If you are leveraging this behavior, it's recommended to enable the future flag, move your splat to it's own route, and leverage
../
for any links to "sibling" pages:This way,
.
means "the full current pathname for my route" in all cases (including static, dynamic, and splat routes) and..
always means "my parents pathname".Patch Changes
@remix-run/router@1.14.0
react-router@6.21.0
v6.20.1
Compare Source
Patch Changes
useResolvedPath
fix for splat routes due to a large number of applications that were relying on the buggy behavior (see https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329). We plan to re-introduce this fix behind a future flag in the next minor version. (#11078)react-router@6.20.1
@remix-run/router@1.13.1
v6.20.0
Compare Source
Minor Changes
PathParam
type from the public API (#10719)Patch Changes
react-router@6.20.0
@remix-run/router@1.13.0
v6.19.0
Compare Source
Minor Changes
unstable_flushSync
option touseNavigate
/useSumbit
/fetcher.load
/fetcher.submit
to opt-out ofReact.startTransition
and intoReactDOM.flushSync
for state updates (#11005)unstable_usePrompt
to accept aBlockerFunction
in addition to aboolean
(#10991)Patch Changes
key
in auseFetcher
that remains mounted wasn't getting picked up (#11009)useFormAction
which was incorrectly inheriting the?index
query param from child routeaction
submissions (#11025)NavLink
active
logic whento
location has a trailing slash (#10734)react-router@6.19.0
@remix-run/router@1.12.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.