@remix-run/router
1.23.4 · 18 Aug 2026MIT24.8M / weekRepositoryHomepagenpmAtom feed
54 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
1.7.2 – 1.23.432 releases without a noteShow each
- 1.23.418 Aug 2026no note
- 1.23.329 May 2026no note
- 1.23.27 Jan 2026no note
- 1.23.113 Nov 2025no note
- 1.23.027 Feb 2025no note
- 1.22.030 Jan 2025no note
- 1.21.116 Jan 2025no note
- 1.21.06 Nov 2024no note
- 1.20.011 Oct 2024no note
- 1.19.29 Sep 2024no note
- 1.19.115 Aug 2024no note
- 1.19.01 Aug 2024no note
- 1.18.016 Jul 2024no note
- 1.17.13 Jul 2024no note
- 1.17.024 Jun 2024no note
- 1.16.110 May 2024no note
- 1.16.023 Apr 2024no note
- 1.15.37 Mar 2024no note
- 1.15.228 Feb 2024no note
- 1.15.116 Feb 2024no note
- 1.15.01 Feb 2024no note
- 1.14.211 Jan 2024no note
- 1.14.121 Dec 2023no note
- 1.14.013 Dec 2023no note
- 1.13.11 Dec 2023no note
- 1.13.022 Nov 2023no note
- 1.12.016 Nov 2023no note
- 1.11.031 Oct 2023no note
- 1.10.016 Oct 2023no note
- 1.9.013 Sep 2023no note
- 1.8.010 Aug 2023no note
- 1.7.217 Jul 2023no note
1.7.1
30 Jun 2023Fix loop in
unstable_useBlockerwhen used with an unstable blocker functionFix issues with reused blockers on subsequent navigations
Patch Changes
Fix loop in
unstable_useBlockerwhen used with an unstable blocker functionFix issues with reused blockers on subsequent navigations
1.7.0
23 Jun 20231.6.3
6 Jun 2023Wrap internal router state updates with
React.startTransitionAllow fetcher revalidations to complete if submitting fetcher is deleted
Re-throw
DOMException(DataCloneError) when attempting to perform aPUSHnavigation with non-serializable state.
Warning
Please use version6.13.0or later instead of6.12.0/6.12.1. These versions suffered from some Webpack build/minification issues resulting failed builds or invalid minified code in your production bundles. See #10569 and #10579 for more details.What's Changed
With
6.12.0we've added better support for suspending components by wrapping the internal router state updates inReact.startTransition. This means that, for example, if one of your components in a destination route suspends and you have not provided aSuspenseboundary to show a fallback, React will delay the rendering of the new UI and show the old UI until that asynchronous operation resolves. This could be useful for waiting for things such as waiting for images or CSS files to load (and technically, yes, you could use it for data loading but we'd still recommend using loaders for that 😀). For a quick overview of this usage, check out Ryan's demo on Twitter.Minor Changes
Wrap internal router state updates with
React.startTransition
Patch Changes
Allow fetcher revalidations to complete if submitting fetcher is deleted
Re-throw
DOMException(DataCloneError) when attempting to perform aPUSHnavigation with non-serializable state.Ensure revalidations happen when hash is present
Upgrade
jestandjsdom
1.6.0
28 Apr 2023Enable
basenamesupport inuseFetcherWhen 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()Fetchers should no longer revalidate on search params changes or routing to the same URL, and will only revalidate on
actionsubmissions orrouter.revalidatecalls
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
1.0.4
30 Nov 2022Throw an error if an
action/loaderfunction returnsundefinedas revalidations need to know whether the loader has previously been executed.undefinedalso causes issues during SSR stringification for hydration. You should always ensure yourloader/actionreturns a value, and you may returnnullif you don't wish to return anything.Preserve the HTTP method on 307/308 redirects
What's Changed
Throw an error if an
action/loaderfunction returnsundefinedas revalidations need to know whether the loader has previously been executed.undefinedalso causes issues during SSR stringification for hydration. You should always ensure yourloader/actionreturns a value, and you may returnnullif you don't wish to return anything.Properly handle redirects to external domains (#9590, #9654)
Preserve the HTTP method on 307/308 redirects
Support
basenamein static data routersEnhanced
ErrorResponsebodies to contain more descriptive text in internal 403/404/405 scenariosFix issues with encoded characters in
NavLinkand descendant<Routes>(#9589, #9647)Properly serialize/deserialize
ErrorResponseinstances when using built-in hydrationSupport
basenamein static data routers
1.0.3
1 Nov 2022Switched back to a caret range for history, now that the warnings have been removed
You may now upgrade your history version to the latest release. NPM will no longer yell at you about versioning and any previous deprecation warnings have been cleared in the 1.17.0 version. Sorry about the confusion!
npm install --save history@1.17.0
Changes
Switched back to a caret range for history, now that the warnings have been removed
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.