-
Notifications
You must be signed in to change notification settings - Fork 1
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 from v6.11.1 to v6.21.1 #319
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
changed the title
Update dependency react-router-dom from v6.11.1 to v6.11.2
Update dependency react-router-dom from v6.11.1 to v6.12.0
Jun 6, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
3 times, most recently
from
June 6, 2023 22:55
32fe181
to
d19cab1
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.12.0
Update dependency react-router-dom from v6.11.1 to v6.12.1
Jun 8, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 8, 2023 20:57
d19cab1
to
05d2b1e
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.12.1
Update dependency react-router-dom from v6.11.1 to v6.13.0
Jun 14, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 14, 2023 17:11
05d2b1e
to
c7b3bc1
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.13.0
Update dependency react-router-dom from v6.11.1 to v6.14.0
Jun 23, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 23, 2023 21:08
c7b3bc1
to
df58265
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.14.0
Update dependency react-router-dom from v6.11.1 to v6.14.1
Jun 30, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 30, 2023 20:12
df58265
to
67500d5
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.14.1
Update dependency react-router-dom from v6.11.1 to v6.14.2
Jul 17, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
July 17, 2023 21:04
67500d5
to
d6cc21e
Compare
Kudos, SonarCloud Quality Gate passed! |
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.14.2
Update dependency react-router-dom from v6.11.1 to v6.15.0
Aug 10, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
August 10, 2023 20:51
d6cc21e
to
db6e8a7
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.15.0
Update dependency react-router-dom from v6.11.1 to v6.16.0
Sep 13, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
September 13, 2023 20:17
db6e8a7
to
7ba4a99
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.16.0
Update dependency react-router-dom from v6.11.1 to v6.17.0
Oct 16, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
October 16, 2023 19:05
7ba4a99
to
68baa90
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.17.0
Update dependency react-router-dom from v6.11.1 to v6.18.0
Nov 1, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 1, 2023 07:59
68baa90
to
f01b2cd
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.18.0
Update dependency react-router-dom from v6.11.1 to v6.19.0
Nov 16, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 16, 2023 16:56
f01b2cd
to
4c1c306
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.19.0
Update dependency react-router-dom from v6.11.1 to v6.20.0
Nov 22, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 22, 2023 18:52
4c1c306
to
381cfac
Compare
renovate
bot
changed the title
Update dependency react-router-dom from v6.11.1 to v6.20.0
Update dependency react-router-dom from v6.11.1 to v6.20.1
Dec 1, 2023
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 1, 2023 19:55
381cfac
to
fb5eac5
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
December 13, 2023 23:36
fb5eac5
to
dfa64e2
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
25 times, most recently
from
January 4, 2024 03:02
c785bad
to
56da5f4
Compare
renovate
bot
force-pushed
the
renovate/react-router-monorepo
branch
from
January 4, 2024 07:31
56da5f4
to
6e3c84d
Compare
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.11.1
->6.21.1
Release Notes
remix-run/react-router (react-router-dom)
v6.21.1
Compare Source
Patch Changes
[email protected]
@remix-run/[email protected]
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/[email protected]
[email protected]
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]
v6.16.0
Compare Source
Minor Changes
@remix-run/[email protected]
[email protected]
Patch Changes
v6.15.0
Compare Source
Minor Changes
redirectDocument()
function which allows users to specify that a redirect from aloader
/action
should trigger a document reload (viawindow.location
) instead of attempting to navigate to the redirected location via React Router (#10705)Patch Changes
URLSearchParams
and theuseSearchParams
hook. (#10620)useFormAction()
for unspecified actions since it cannot be determined on the server and causes hydration issues (#10758)unstable_usePrompt
to avoid throwing an exception if the prompt is unblocked and a navigation is performed synchronously (#10687, #10718)@remix-run/[email protected]
[email protected]
v6.14.2
Compare Source
Patch Changes
<ScrollRestoration>
(#10682)<Form state>
prop to populatehistory.state
on submission navigations (#10630)Error
subclasses such asReferenceError
/TypeError
(#10633)@remix-run/[email protected]
[email protected]
v6.14.1
Compare Source
Patch Changes
[email protected]
@remix-run/[email protected]
v6.14.0
Compare Source
Minor Changes
Add support for
application/json
andtext/plain
encodings foruseSubmit
/fetcher.submit
. To reflect these additional types,useNavigation
/useFetcher
now also containnavigation.json
/navigation.text
andfetcher.json
/fetcher.text
which include the json/text submission if applicable (#10413)Patch Changes
submitter
element, prefer the built-innew FormData(form, submitter)
instead of the previous manual approach in modern browsers (those that support the newsubmitter
parameter) (#9865, #10627)type="image"
buttonsformdata-submitter-polyfill
window.history.pushState/replaceState
before updating React Router state (instead of after) so thatwindow.location
matchesuseLocation
during synchronous React 17 rendering (#10448)window.location
and should always referenceuseLocation
when possible, aswindow.location
will not be in sync 100% of the time (due topopstate
events, concurrent mode, etc.)tsc --skipLibCheck:false
issues on React 17 (#10622)typescript
to 5.1 (#10581)[email protected]
@remix-run/[email protected]
v6.13.0
Compare Source
Minor Changes
Move
React.startTransition
usage behind a future flag to avoid issues with existing incompatibleSuspense
usages. We recommend folks adopting this flag to be better compatible with React concurrent mode, but if you run into issues you can continue without the use ofstartTransition
until v7. Issues usually boils down to creating net-new promises during the render cycle, so if you run into issues you should either lift your promise creation out of the render cycle or put it behind auseMemo
. (#10596)Existing behavior will no longer include
React.startTransition
:If you wish to enable
React.startTransition
, pass the future flag to your component:Patch Changes
React.startTransition
minification bug in production mode (#10588)[email protected]
v6.12.1
Compare Source
Patch Changes
React.startTransition
to fix webpack + react 17 compilation error (#10569)[email protected]
v6.12.0
Compare Source
Minor Changes
React.startTransition
if it exists (#10438)Patch Changes
DOMException
(DataCloneError
) when attempting to perform aPUSH
navigation with non-serializable state. (#10427)@remix-run/[email protected]
[email protected]
v6.11.2
Compare Source
Patch Changes
SetURLSearchParams
type (#10444)[email protected]
@remix-run/[email protected]
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.