chore(deps): update dependency react-router-dom to ^6.16.0 #1704
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.10.0
->^6.16.0
Release Notes
remix-run/react-router (react-router-dom)
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]
v6.11.1
Compare Source
Patch Changes
[email protected]
@remix-run/[email protected]
v6.11.0
Compare Source
Minor Changes
basename
support inuseFetcher
(#10336)basename
then you will need to remove the manually prependedbasename
from yourfetcher
calls (fetcher.load('/basename/route') -> fetcher.load('/route')
)Patch Changes
Component
instead ofelement
on a route definition (#10287)<Link to="//">
and other invalid URL values (#10367)useSyncExternalStore
touseState
for internal@remix-run/router
router state syncing in<RouterProvider>
. We found some subtle bugs where router state updates got propagated before other normaluseState
updates, which could lead to footguns inuseEffect
calls. (#10377, #10409)StaticRouterProvider
's internalRouter
component (#10401)RouterProvider
,useNavigate
/useSubmit
/fetcher.submit
are now stable across location changes, since we can handle relative routing via the@remix-run/router
instance and get rid of our dependence onuseLocation()
. When usingBrowserRouter
, these hooks remain unstable across location changes because they still rely onuseLocation()
. (#10336)[email protected]
@remix-run/[email protected]
Configuration
📅 Schedule: Branch creation - "after 4:00 am on Friday on the 1st through 7th day of the month every 3 month" in timezone Australia/Melbourne, 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.