-
Notifications
You must be signed in to change notification settings - Fork 60
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 react-router monorepo to v6.23.1 #639
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/react-router-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #639 +/- ##
=======================================
Coverage 92.86% 92.86%
=======================================
Files 160 160
Lines 3322 3322
Branches 888 893 +5
=======================================
Hits 3085 3085
+ Misses 219 218 -1
- Partials 18 19 +1 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
January 9, 2024 07:32
c809bb6
to
8df2de7
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
4 times, most recently
from
January 11, 2024 16:22
8d82b01
to
7520859
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo to v6.21.1
fix(deps): update react-router monorepo
Jan 11, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
January 11, 2024 20:24
7520859
to
d5673ed
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo
fix(deps): update react-router monorepo to v6.21.2
Jan 11, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
6 times, most recently
from
January 18, 2024 22:45
009b67b
to
1360478
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo to v6.21.2
fix(deps): update react-router monorepo to v6.21.3
Jan 18, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
3 times, most recently
from
January 25, 2024 13:59
4bbccf0
to
78479e4
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
5 times, most recently
from
February 1, 2024 21:55
9e1ab9d
to
64c3fd8
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo to v6.21.3
fix(deps): update react-router monorepo to v6.22.0
Feb 1, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 2, 2024 22:01
64c3fd8
to
5e97cc4
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
3 times, most recently
from
February 16, 2024 21:26
728acea
to
bb199e5
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
February 28, 2024 21:29
c93b68b
to
8b69b24
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo to v6.22.1
fix(deps): update react-router monorepo to v6.22.2
Feb 28, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
March 7, 2024 17:37
8b69b24
to
2a5bbdc
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo to v6.22.2
fix(deps): update react-router monorepo to v6.22.3
Mar 7, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
March 25, 2024 10:11
b3bbebe
to
530db5a
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
April 4, 2024 07:45
0926d25
to
04cd598
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
5 times, most recently
from
April 8, 2024 18:45
dbad631
to
7baac3c
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
April 23, 2024 20:03
7baac3c
to
d0e7940
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo to v6.22.3
fix(deps): update react-router monorepo to v6.23.0
Apr 23, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
May 10, 2024 20:05
0392d66
to
2651313
Compare
renovate
bot
changed the title
fix(deps): update react-router monorepo to v6.23.0
fix(deps): update react-router monorepo to v6.23.1
May 10, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
May 17, 2024 12:42
320cbea
to
659fbf7
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
4 times, most recently
from
May 28, 2024 13:16
fc93422
to
b16b238
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
June 11, 2024 13:27
b670f68
to
abf874c
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 17, 2024 15:04
abf874c
to
53953ea
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:
6.18.0
->6.23.1
6.18.0
->6.23.1
Release Notes
remix-run/react-router (react-router)
v6.23.1
Compare Source
Patch Changes
<Await>
(#11513)@remix-run/router@1.16.1
v6.23.0
Compare Source
Minor Changes
unstable_dataStrategy
configuration option (#11098)Patch Changes
@remix-run/router@1.16.0
v6.22.3
Compare Source
Patch Changes
@remix-run/router@1.15.3
v6.22.2
Compare Source
Patch Changes
@remix-run/router@1.15.2
v6.22.1
: v6.22.1Compare Source
See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6221
v6.22.0
Compare Source
Patch Changes
@remix-run/router@1.15.0
v6.21.3
Compare Source
Patch Changes
unstable_
prefix fromBlocker
/BlockerFunction
types (#11187)v6.21.2
Compare Source
v6.21.1
Compare Source
Patch Changes
route.lazy
not working correctly on initial SPA load whenv7_partialHydration
is specified (#11121)@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
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)@remix-run/router@1.13.1
v6.20.0
Compare Source
Minor Changes
PathParam
type from the public API (#10719)Patch Changes
resolveTo
in splat routes (#11045)getPathContributingMatches
UNSAFE_getPathContributingMatches
export from@remix-run/router
since we no longer need this in thereact-router
/react-router-dom
layers@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_
prefix from theuseBlocker
hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix fromunstable_usePrompt
due to differences in how browsers handlewindow.confirm
that prevent React Router from guaranteeing consistent/correct behavior. (#10991)Patch Changes
Fix
useActionData
so it returns proper contextual action data and not any action data in the tree (#11023)Fix bug in
useResolvedPath
that would causeuseResolvedPath(".")
in a splat route to lose the splat portion of the URL path. (#10983)"."
paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via"."
inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.Updated dependencies:
@remix-run/router@1.12.0
remix-run/react-router (react-router-dom)
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 - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.