-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update dependency react-router-dom to v6.23.0 #600
Merged
Merged
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
force-pushed
the
renovate/react-router-monorepo
branch
3 times, most recently
from
October 29, 2023 02:54
b4e3a61
to
1fe6308
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.17.0
Update dependency react-router-dom to v6.18.0
Oct 31, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
November 5, 2023 09:47
440dcac
to
71cf011
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.18.0
Update dependency react-router-dom to v6.19.0
Nov 16, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 16, 2023 15:53
71cf011
to
fdadcc0
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.19.0
Update dependency react-router-dom to v6.20.0
Nov 22, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 22, 2023 20:11
fdadcc0
to
fd53c99
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.20.0
Update dependency react-router-dom to v6.20.1
Dec 1, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
December 2, 2023 07:33
9a4a66f
to
61669f7
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.20.1
Update dependency react-router-dom to v6.21.0
Dec 14, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 14, 2023 02:48
61669f7
to
a8dbb52
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.21.0
Update dependency react-router-dom to v6.21.1
Dec 21, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 21, 2023 17:08
a8dbb52
to
948fbb2
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
January 10, 2024 09:48
948fbb2
to
b392b9b
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.21.1
Update dependency react-router-dom to v6.21.2
Jan 11, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
January 11, 2024 17:53
b392b9b
to
235402b
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
January 18, 2024 22:59
235402b
to
5bc94e1
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.21.2
Update dependency react-router-dom to v6.21.3
Jan 18, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 1, 2024 22:47
5bc94e1
to
b2f02dd
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.21.3
Update dependency react-router-dom to v6.22.0
Feb 1, 2024
renovate
bot
changed the title
Update dependency react-router-dom to v6.22.0
Update dependency react-router-dom to v6.22.1
Feb 16, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 16, 2024 22:53
b2f02dd
to
8ad4cd9
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.22.1
Update dependency react-router-dom to v6.22.2
Feb 28, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
February 28, 2024 21:20
8ad4cd9
to
c6a5d78
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.22.2
Update dependency react-router-dom to v6.22.3
Mar 7, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
March 7, 2024 15:37
c6a5d78
to
195b604
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
April 23, 2024 16:40
195b604
to
fbde701
Compare
renovate
bot
changed the title
Update dependency react-router-dom to v6.22.3
Update dependency react-router-dom to v6.23.0
Apr 23, 2024
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
April 27, 2024 09:40
fbde701
to
99641d1
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.16.0
->6.23.0
Release Notes
remix-run/react-router (react-router-dom)
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
v6.18.0
Compare Source
Minor Changes
Add support for manual fetcher key specification via
useFetcher({ key: string })
so you can access the same fetcher instance from different components in your application without prop-drilling (RFC) (#10960)useFetchers
so that they can be looked up bykey
Add
navigate
/fetcherKey
params/props touseSumbit
/Form
to support kicking off a fetcher submission under the hood with an optionally user-specifiedkey
(#10960)useFetcher({ key })
to look it up elsewherePatch Changes
RouterProvider
that holds completed fetcher data, in preparation for the upcoming future flag that will change the fetcher persistence/cleanup behavior (#10961)future
prop onBrowserRouter
,HashRouter
andMemoryRouter
so that it accepts aPartial<FutureConfig>
instead of requiring all flags to be included. (#10962)@remix-run/router@1.11.0
react-router@6.18.0
v6.17.0
Compare Source
Minor Changes
Add experimental support for the View Transitions API via
document.startViewTransition
to enable CSS animated transitions on SPA navigations in your application. (#10916)The simplest approach to enabling a View Transition in your React Router app is via the new
<Link unstable_viewTransition>
prop. This will cause the navigation DOM update to be wrapped indocument.startViewTransition
which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.If you need to apply more fine-grained styles for your animations, you can leverage the
unstable_useViewTransitionState
hook which will tell you when a transition is in progress and you can use that to apply classes or styles:You can also use the
<NavLink unstable_viewTransition>
shorthand which will manage the hook usage for you and automatically add atransitioning
class to the<a>
during the transition:For an example usage of View Transitions with React Router, check out our fork of the Astro Records demo.
For more information on using the View Transitions API, please refer to the Smooth and simple transitions with the View Transitions API guide from the Google Chrome team.
Please note, that because the
ViewTransition
API is a DOM API, we now export a specificRouterProvider
fromreact-router-dom
with this functionality. If you are importingRouterProvider
fromreact-router
, then it will not support view transitions. (#10928Patch Changes
ScrollRestoration
whensessionStorage
is unavailable (#10848)@remix-run/router@1.10.0
react-router@6.17.0
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 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 Mend Renovate. View repository job log here.