react-router-native
Advanced tools
Changelog
v6.28.1
Date: 2024-12-20
false
(#12441)Full Changelog: v6.28.0...v6.28.1
Changelog
v6.28.0
Date: 2024-11-06
json
/defer
in favor of returning raw objects
Full Changelog: v6.27.0...v6.28.0
Changelog
v6.27.0
Date: 2024-10-11
This release stabilizes a handful of "unstable" APIs in preparation for the pending React Router v7 release (see these posts for more info):
unstable_dataStrategy
→ dataStrategy
(createBrowserRouter
and friends) (Docs)unstable_patchRoutesOnNavigation
→ patchRoutesOnNavigation
(createBrowserRouter
and friends) (Docs)unstable_flushSync
→ flushSync
(useSubmit
, fetcher.load
, fetcher.submit
) (Docs)unstable_viewTransition
→ viewTransition
(<Link>
, <Form>
, useNavigate
, useSubmit
) (Docs)unstable_flushSync
option for navigations and fetchers (#11989)unstable_viewTransition
option for navigations and the corresponding unstable_useViewTransitionState
hook (#11989)unstable_dataStrategy
(#11974)unstable_patchRoutesOnNavigation
(#11973)
PatchRoutesOnNavigationFunctionArgs
type for convenience (#11967)?index
param already exists from a prior submission (#12003)useFormAction
bug - when removing ?index
param it would not keep other non-Remix index
params (#12003)preventScrollReset
through redirects during concurrent fetches (#11999)console.error
on fetcher abort due to back-to-back revalidation calls (#12050)partialHydration
when hydrating with errors (#12070)patchRoutesOnNavigation
calls (#12055)
unstable_
APIpatchRoutesOnNavigation
internally so that multiple navigations with the same start/end would only execute the function once and use the same promisepatch
short circuiting if a navigation was interrupted (and the request.signal
aborted) since the first invocation's patch
would no-opimport()
for async routes will already be cached automatically - and if not it's easy enough for users to implement this cache in userlanddiscoveredRoutes
FIFO queue from unstable_patchRoutesOnNavigation
(#11977)
unstable_
APIpatchRoutesOnNavigation
RouteObject
within PatchRoutesOnNavigationFunction
's patch
method so it doesn't expect agnostic route objects passed to patch
(#11967)patchRoutesOnNavigation
directly to useRouteError
instead of wrapping them in a 400 ErrorResponse
instance (#12111)Full Changelog: v6.26.2...v6.27.0