Packages

@remix-run/router

1.23.4 · 18 Aug 2026MIT24.8M / weekRepositoryHomepagenpmAtom feed

Your version

1.6.0

28 Apr 2023Where it was published

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

Release note

What's Changed

Minor Changes

  • Enable basename support in useFetcher

    • If you were previously working around this issue by manually prepending the basename then you will need to remove the manually prepended basename from your fetcher calls (fetcher.load('/basename/route') -> fetcher.load('/route'))

Patch Changes

  • When using a 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 on useLocation()

    • When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation()

  • Fetchers should no longer revalidate on search params changes or routing to the same URL, and will only revalidate on action submissions or router.revalidate calls

  • Fix inadvertent re-renders when using Component instead of element on a route definition

  • Fail gracefully on <Link to="//"> and other invalid URL values

  • Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to foot guns in useEffect calls. (#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> when RouterProvider errors existed

  • Fix detection of useNavigate in the render cycle by setting the activeRef in a layout effect, allowing the navigate function to be passed to child components and called in a useEffect there

  • Allow useRevalidator() to resolve a loader-driven error boundary scenario

  • Enhance LoaderFunction/ActionFunction return type to prevent undefined from being a valid return value

  • Ensure proper 404 error on fetcher.load call to a route without a loader

  • Decouple AbortController usage 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.