Packages

@remix-run/router

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

Upgrading @remix-run/router From 0.1.0 to 1.23.4

53 releases in betweennotes for 8

Other targets from 0.1.0Clears its advisory1.23.2
The note of 1.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 0.1.0yours
  2. 1.0.0major
  3. 51 releases
  4. 1.23.4target
?
changes to make
1
advisory fixed
7+
new
17+
fixes

Counted from 8 of 53 release notes. Advisories are counted from the advisory database, in full.

Security

Fixes 1 advisory affecting 0.1.0

Release by release

  1. 1.7.2 – 1.23.432 releases, no release note

  2. 1.7.1

    30 Jun 20232 fixes
    • Fixed

      Fix loop in unstable_useBlocker when used with an unstable blocker function

    • Fixed

      Fix issues with reused blockers on subsequent navigations

  3. 1.7.0no release note

  4. 1.6.3

    6 Jun 20232 new · 3 fixes
    • New

      Wrap internal router state updates with React.startTransition

    • New

      Allow fetcher revalidations to complete if submitting fetcher is deleted

    • Fixed

      Re-throw DOMException (DataCloneError) when attempting to perform a PUSH navigation with non-serializable state.

    • Fixed

      Ensure revalidations happen when hash is present

    • Fixed

      Upgrade jest and jsdom

  5. 1.6.1 – 1.6.22 releases, no release note

  6. 1.6.0

    28 Apr 20232 new · 11 fixes
    • New

      Enable basename support in useFetcher

    • New

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

    • Fixed

      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()

    • Fixed

      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

  7. 1.0.5 – 1.5.010 releases, no release note

  8. 1.0.4

    30 Nov 20221 new · 1 fix
    • New

      Support basename in static data routers

    • Fixed

      Fix issues with encoded characters in NavLink and descendant <Routes> (#9589, #9647)

7 other lines we could not sort, mostly version bumps
  • Throw an error if an action/loader function returns undefined as revalidations need to know whether the loader has previously been executed. undefined also causes issues during SSR stringification for hydration. You should always ensure your loader/action returns a value, and you may return null if you don't wish to return anything.

    1.0.4
  • Properly handle redirects to external domains (#9590, #9654)

    1.0.4
  • Preserve the HTTP method on 307/308 redirects

    1.0.4
  • Enhanced ErrorResponse bodies to contain more descriptive text in internal 403/404/405 scenarios

    1.0.4
  • Properly serialize/deserialize ErrorResponse instances when using built-in hydration

    1.0.4
  • Switched back to a caret range for history, now that the warnings have been removed

    1.0.3
  • Pinned peer dependency on History to 1.13.x to avoid console warnings.

    1.0.2

5 internal lines (docs, tests, tooling) left out.

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.