-
-
Notifications
You must be signed in to change notification settings - Fork 721
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
chore(deps): update react-router monorepo to v6.20.1 #5536
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 8, 2023 08:09
bb9bd61
to
ce91d8f
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 8, 2023 22:51
ce91d8f
to
c5df3a9
Compare
renovate
bot
changed the title
chore(deps): update react-router monorepo to v6.20.0
chore(deps): update react-router monorepo to v6.20.1
Dec 8, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 11, 2023 09:47
c5df3a9
to
0b4885c
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 11, 2023 10:27
0b4885c
to
d891870
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 11, 2023 10:49
d891870
to
8c4a758
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
4 times, most recently
from
December 11, 2023 11:36
2201a21
to
abf79ed
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
December 11, 2023 12:13
7b8ab1e
to
abbb41e
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 19, 2023 12:47
112e316
to
e307ac0
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 19, 2023 13:11
e307ac0
to
973ed3f
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 19, 2023 14:03
973ed3f
to
2a93cdd
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 19, 2023 14:37
2a93cdd
to
74cf578
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
2 times, most recently
from
December 19, 2023 19:05
8d14819
to
71bca96
Compare
vercel
bot
temporarily deployed
to
Preview – unleash-monorepo-frontend
December 19, 2023 19:17
Inactive
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 19, 2023 19:18
71bca96
to
db36777
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 20, 2023 07:17
db36777
to
018814e
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 20, 2023 08:18
018814e
to
09ecba1
Compare
thomasheartman
approved these changes
Dec 20, 2023
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.20.1
6.16.0
->6.20.1
Release Notes
remix-run/react-router (react-router)
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/[email protected]
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/[email protected]
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/[email protected]
v6.18.0
Compare Source
Patch Changes
future
prop onBrowserRouter
,HashRouter
andMemoryRouter
so that it accepts aPartial<FutureConfig>
instead of requiring all flags to be included. (#10962)@remix-run/[email protected]
v6.17.0
Compare Source
Patch Changes
RouterProvider
future
prop type to be aPartial<FutureConfig>
so that not all flags must be specified (#10900)@remix-run/[email protected]
remix-run/react-router (react-router-dom)
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)[email protected]
@remix-run/[email protected]
v6.20.0
Compare Source
Minor Changes
PathParam
type from the public API (#10719)Patch Changes
[email protected]
@remix-run/[email protected]
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)[email protected]
@remix-run/[email protected]
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/[email protected]
[email protected]
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/[email protected]
[email protected]
Configuration
📅 Schedule: Branch creation - "after 7pm every weekday,before 5am every weekday" in timezone Europe/Madrid, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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.