Renovate: Update dependency react-router to v8.5.2 #66
No reviewers
Doble/Owners
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
Renovate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Doble/MatchingMakingSite!66
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/react-router-8.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
8.3.0→8.5.2Release Notes
remix-run/react-router (react-router)
v8.5.2Compare Source
Patch Changes
dataStrategynavigation types and loading navigation history actionsHEADrequests, so a resource route streaming a file no longer leaks its file descriptor (#15634)<Suspense>boundaries during hydration in development (#15382)React.startTransitionto prevent React 19 from silently discarding the server HTML and rendering the boundary on the clientbasenameis configured (#15725)href()to throw fornullrequired parameters and omitnullsplat parameters without a trailing slash, matching the behavior forundefinedand the defined types (#15754)MetaArgs.matchestypes to stop at the current route instead of appending an unknown, possibly undefined tail (#15697)href(),generatePath(), links, forms, fetchers, and redirects (#15785)redirect(),redirectDocument()andreplace()from settingstatus: 302on theResponseInitpassed to them (#15753)<Await>render error when it receives a newresolvevalue, so the error element no longer stays on screen after navigating to a route whose data renders fine (#15695)clientMiddlewareduring RSC client navigations and preserve it when route components update via HMR (#15763)HEADresource responses consistently in RSC Framework and RSC Data modes (#15783)clientLoaderand noHydrateFallback(#15763)<ScrollRestoration>throwing an uncaught error before hydration whensessionStorageis unavailable (#15566)sessionStorageagain and threw (e.g. Chrome with "Block all cookies", sandboxed cross-origin iframes)console.error; only the second, uncaught throw is removeduseBlockerleaving behind a stale blocker that keeps blocking navigation after its component is hidden and shown again with<Activity>, or after the router is recreated (#15710)v8.5.1Compare Source
Patch Changes
URIError: URI malformedwhen anssr: falsedev server receives a URL path with a malformed percent-encoding (#15649)<Form>to the current URL with an encodedaction(#15679)actioncontains characters that get percent-encoded, such as spaces or non-ASCII charactersviewTransitionnavigation, for example in a hidden tab (#15582)lazy.Componentimports on loader-less routes to the nearest error boundary (#15658)lazyroute imports instead of caching failures permanently (#15689)shouldRevalidateidlewhen a revalidation completes a pending navigation started by another fetcher's redirectdocument.startViewTransition()overload to the globalDocumenttype (#15680)ViewTransitiontypedeleteDataindestroySessionwhen the session has no ID (#15639).datafiles for hydrating routes with a serverloaderin anssr: falseapp with aprerenderconfigUnstable Changes
⚠️ Unstable features are not recommended for production use
<Await unstable_promise={promise}>implementation based on React'suse()API (#15678)React.useinstead of React Router's internal promise trackingerrorElement,useAsyncValue, anduseAsyncErrorsupporterrorElementwhen usingunstable_promise, allowing child render errors to bubble to the nearest React error boundaryReact.use()URIError: URI malformedwhen an API-only (ssr: "unstable_api-only") server receives a URL path with a malformed percent-encoding (#15649)v8.5.0Compare Source
Minor Changes
<ViewTransition>component, available in React 19.3 and later (#15493)viewTransitionprops/options,useViewTransitionState, andNavLink'sisTransitioningrender prop andtransitioningclassPatch Changes
<Await>failing to server render promises decoded from an RSC payload, which caused the Suspense boundary to switch to client rendering (#15597)@types/reactand@types/react-domas optional peer dependencies so the shipped type definitions resolve React types under strict (non-hoisted) node_modules layouts (#15528)unstable_useRouterStatedocumentation example to call the imported alias (#15535)HydrateFallbackof a route discovered throughpatchRoutesOnNavigationduring initial hydration (#15537)state.matcheswhile their loaders run, so<RouterProvider>renders down to the discovered route'sHydrateFallbackinstead of rendering nothingRouterProvidersubscribes, including when other subscribers are already attached, and report current client errors once without replaying server errors during hydration (#15637)matchPathnot treating a static segment as optional when it contains characters outside[\w-](#15425)fetcher.reset(), so its cleared data no longer comes back on the next revalidation (#15633)Unstable Changes
⚠️ Unstable features are not recommended for production use
unstable_fetchprop to<HydratedRouter>to customize JavaScript-issued manifest and server data requests in conventional Framework Mode (#15586)navigationType("PUSH","REPLACE", or"POP"for navigation-initiated requests, including reloaded fetchers;nullotherwise)unstable_initiatorandunstable_navigationTypetypeto"navigation"guarantees a non-nullnavigationType, while other data requests have anullnavigationType"initialization"type and include their fetcher key<Link prefetch>use native<link rel="prefetch">elements and do not call the custom implementationunstable_useRouteDiscoveryfor application-controlled route discovery in conventional Framework Mode (#15602)loadAllRoutes()future.unstable_customRouteDiscoveryto opt inevent.defaultBehavior()from a custom mismatch handler to explicitly run built-in recoverynext()v8.4.0Compare Source
Minor Changes
createStaticRouter({ branches })option (#15297)createStaticRouternow caches route branches internally, ignoresbranches, and logs a deprecation warning when the option is providedEntryContext.branchesproperty remains available for compatibility but is always an empty arrayPatch Changes
dataStrategyresult error (#15464)UNSAFE_contexts, so please review carefully if you are using those unsafe exportsdocument.startViewTransitioncalls during initial hydration androuter.revalidate()calls (#15484)SingleFetchNoResultErrorthrown when a fetcher revalidates against a splat route during lazy route discovery (#15395)causeof theUnable to decode turbo-stream responseerror (#15450)Unstable Changes
⚠️ Unstable features are not recommended for production use
future.unstable_routePatternMatchingflag for more efficient route matching powered by@remix-run/route-pattern(#15298)unstable_validateParamsroute field to reject invalid parameter values and continue matchingv8.3.1Compare Source
Patch Changes
Expected fetcher: <key>error thrown on navigation when a fetcher is aborted during its post-action revalidation (#15365)<ScrollRestoration>leavinghistory.scrollRestorationset to"auto"after a bfcache restore, which let the browser restore scroll on subsequent history traversals before the destination route had rendered (#15397)relativeoption inuseSubmit/fetcher.submitwhen resolivng theactionpath (#15400)Configuration
📅 Schedule: (UTC)
🚦 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 CLI.
289f6b2e7739cfe09ba8Renovate: Update dependency react-router to v8.3.1to Renovate: Update dependency react-router to v8.4.039cfe09ba8a64793a14aRenovate: Update dependency react-router to v8.4.0to Renovate: Update dependency react-router to v8.5.0a64793a14ae58a8dc08fRenovate: Update dependency react-router to v8.5.0to Renovate: Update dependency react-router to v8.5.1e58a8dc08fcfefb62392Renovate: Update dependency react-router to v8.5.1to Renovate: Update dependency react-router to v8.5.2View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.