@remix-run/router
1.23.4 · 18 Aug 2026MIT24.8M / weekRepositoryHomepagenpmAtom feed
1.23.4 is the newest release of 1.x.
In short
2 new11 fixed1 internal
Security
2 advisories affect 1.6.0; 1.23.3 fixes them
- HighReact Router vulnerable to XSS via Open RedirectsGHSA-2w69-qvjg-hvjx · 8 Jan 2026Fixed in 1.23.2
- ModerateReact Router's same-origin redirect with path starting // causes open redirect via protocol-relative URL reinterpretationGHSA-2j2x-hqr9-3h42 · 3 Jun 2026Fixed in 1.23.3
Release note
What's Changed
Minor Changes
Enable
basenamesupport inuseFetcherIf you were previously working around this issue by manually prepending the
basenamethen you will need to remove the manually prependedbasenamefrom yourfetchercalls (fetcher.load('/basename/route') -> fetcher.load('/route'))
Patch Changes
When using a
RouterProvider,useNavigate/useSubmit/fetcher.submitare now stable across location changes, since we can handle relative routing via the@remix-run/routerinstance and get rid of our dependence onuseLocation()When using
BrowserRouter, these hooks remain unstable across location changes because they still rely onuseLocation()
Fetchers should no longer revalidate on search params changes or routing to the same URL, and will only revalidate on
actionsubmissions orrouter.revalidatecallsFix inadvertent re-renders when using
Componentinstead ofelementon a route definitionFail gracefully on
<Link to="//">and other invalid URL valuesSwitched from
useSyncExternalStoretouseStatefor internal@remix-run/routerrouter state syncing in<RouterProvider>. We found some subtle bugs where router state updates got propagated before other normaluseStateupdates, which could lead to foot guns inuseEffectcalls. (#10377, #10409)Log loader/action errors caught by the default error boundary to the console in dev for easier stack trace evaluation
Fix bug preventing rendering of descendant
<Routes>whenRouterProvidererrors existedFix detection of
useNavigatein the render cycle by setting theactiveRefin a layout effect, allowing thenavigatefunction to be passed to child components and called in auseEffectthereAllow
useRevalidator()to resolve a loader-driven error boundary scenarioEnhance
LoaderFunction/ActionFunctionreturn type to preventundefinedfrom being a valid return valueEnsure proper 404 error on
fetcher.loadcall to a route without aloaderDecouple
AbortControllerusage between revalidating fetchers and the thing that triggered them such that the unmount/deletion of a revalidating fetcher doesn't impact the ongoing triggering navigation/revalidation
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.