@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
- ?
- 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
- React Router vulnerable to XSS via Open Redirectshigh · GHSA-2w69-qvjg-hvjx
Release by release
1.7.2 – 1.23.432 releases, no release note
- Fixed
Fix loop in
unstable_useBlockerwhen used with an unstable blocker function - Fixed
Fix issues with reused blockers on subsequent navigations
- Fixed
1.7.0no release note
- 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 aPUSHnavigation with non-serializable state. - Fixed
Ensure revalidations happen when hash is present
- Fixed
Upgrade
jestandjsdom
- New
1.6.1 – 1.6.22 releases, no release note
- New
Enable
basenamesupport inuseFetcher - New
Allow
useRevalidator()to resolve a loader-driven error boundary scenario - Fixed
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() - Fixed
Fetchers should no longer revalidate on search params changes or routing to the same URL, and will only revalidate on
actionsubmissions orrouter.revalidatecalls
- New
1.0.5 – 1.5.010 releases, no release note
7 other lines we could not sort, mostly version bumps
- 1.0.4
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. - 1.0.4
- 1.0.4
Preserve the HTTP method on 307/308 redirects
- 1.0.4
Enhanced
ErrorResponsebodies to contain more descriptive text in internal 403/404/405 scenarios - 1.0.4
Properly serialize/deserialize
ErrorResponseinstances when using built-in hydration - 1.0.3
Switched back to a caret range for history, now that the warnings have been removed
- 1.0.2
Pinned peer dependency on History to
1.13.xto avoid console warnings.
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.