Releases of @tanstack/react-router

947 stable releases, newest first. Release notes are kept for the last 90 days; older ones link to where they were published.

1. 1.170.44

   12 October 2026

   Patch Changes

   • Updated dependencies:

     • @tanstack/router-core@1.171.37

2. 1.170.43

   12 October 2026

   Patch Changes

   • Updated dependencies:

     • @tanstack/router-core@1.171.36

3. 1.170.42

   10 October 2026

   Patch Changes

   • reduce component nesting per route match

   • Links of a route that the pending navigation leaves skip deriving the destination location, and clicks and preloads follow the href a Link displays. buildLocation now builds mask and routeMasks locations from the same _fromLocation as the destination.

   • Fixed Link destinations that resolve to a route mask are now reused across navigations instead of being rebuilt every time. A mounted Link now follows changes to its href and reloadDocument props, and React Links no longer each subscribe to a hydration flag.

   Show all 8 lines

4. 1.170.41

   30 September 2026

   Patch Changes

   • Compose only enabled route boundaries instead of rendering inactive wrapper components.

   • Update TanStack Store to 0.11.2 to prevent unrelated atom reads inside subscription observers from triggering extra notifications.

   • Consolidate the root match context provider while preserving match context in the root shell.

   Show all 7 lines

5. 1.170.40

   27 September 2026

   Patch Changes

   • Skip unused Link preload cleanup when preloading is disabled and ignore queued viewport notifications after their effect has been cleaned up.

   • Updated dependencies:

     • @tanstack/router-core@1.171.33

6. 1.170.39

   23 September 2026

   Patch Changes

   • Avoid hydration-triggered rerenders for links that do not compare URL hashes while preserving hash-sensitive active state and ClientOnly behavior.

7. 1.170.38

   16 September 2026

   Patch Changes

   • Updated dependencies:

     • @tanstack/router-core@1.171.32

8. 1.170.37

   16 September 2026

   Patch Changes

   • deepEqual now takes its flags as positional arguments — deepEqual(a, b, partial?, explicitUndefined?) — instead of an options object. The router's hot callers (Link option stabilization and active-state checks, matchRoute) no longer allocate an options object per comparison, and the comparator reads two booleans instead of a polymorphic object. explicitUndefined replaces ignoreUndefined: false. deepEqual is an internal helper; it stays exported for compatibility of two-argument calls.

   • resolvePath (internal helper) now takes positional arguments — resolvePath(base, to, trailingSlash?, cache?) — so buildLocation and matchRoute no longer allocate an options object per path resolution.

   • Stream large deferred SSR hydration payloads through a backpressure-aware router transport, fail known setup errors before response creation, and close cancelled or expired transforms safely.

     Start now cancels discarded middleware and HEAD response bodies, including plain streams and derived branches.

     Server-function raw streams share one ordered response. Arbitrary or sequential consumption can require potentially unbounded buffering of unread data on the client. Cancelling one raw stream discards it locally, while aborting the whole call cancels the response and server work. Consume streams concurrently, cancel unused streams promptly, or use separate calls when independent backpressure is required. A raw stream that exceeds its unread-byte limit now fails alone; sibling streams and the JSON result keep flowing.

     The JSON wire shape of a RawStream server-function argument changed. Clients and servers must run matching versions for requests that pass a RawStream.

     The frame-protocol constants (FRAME_TYPE_*, MAX_FRAME_PAYLOAD_SIZE, MAX_FRAMED_STREAMS) moved from the @tanstack/start-client-core root to the @tanstack/start-client-core/client-rpc subpath.

     Router requests whose Accept header allows neither text/html nor */* now receive 406 Not Acceptable instead of 500.

     Framework adapters share the body <Scripts> composition (getSsrBodyScriptParts, composeSsrBodyScripts) and the eager HTML response wrapper (renderSsrHtmlResponse) from @tanstack/router-core.

     Solid SSR now emits one document type and renders late lazy errors through route boundaries. A Solid <Await> without a fallback no longer holds the streamed shell; it renders inside the nearest <Suspense> boundary like React and Vue, and now renders falsy resolved values.

     Static server functions decode cached RawStream values with the client deserializer plugins.

     SSR Query integrations now keep request cleanup and stream ownership aligned with the router lifecycle.

   Show all 7 lines

9. 1.170.36

   13 September 2026

   Patch Changes

   • Keep the Link location cache out of server bundles: buildLocation only creates, reads and writes it when isServer is false. Render React Links on the server without the extra prop copies and the forwarded-ref hook. Link SSR rendering is 20-40% faster in the Link benchmarks and the React Start SSR request loop about 7% faster.

     React activeProps and inactiveProps now follow one precedence rule on every link, including links whose destination is blocked for using a disallowed scheme: state props override element props, ref and event handlers, while href, disabled and target stay controlled by the router. Previously a blocked link ignored a ref or handler from its inactive props.

     React Link and useLinkProps split router options from element props with one key set on the client and the server. Element props pass through as given: external links forward them verbatim, falsy values included, and useLinkProps now returns children for router-controlled links as it already did for external ones.

   • Reuse hydration snapshot getters to avoid unnecessary store-instance effect updates when Links and other hydration-aware components rerender.

   • Allow active and inactive Link props to override base element props in React and Solid while preserving class/style merging. Keep React's href, target, and disabled values controlled by routing options. Preserve Vue object and nested-array class bindings, including reactive updates and server rendering, without mutating cached bindings during VNode normalization.

   Show all 12 lines

10. 1.170.35

    10 September 2026

    Patch Changes

    • Upgrade TanStack Store to 0.11 and migrate router subscriptions to useSelector, preserving selector comparisons and Vue subscription cleanup.

11. 1.170.34

    9 September 2026

    Patch Changes

    • Avoid allocating event-handler arrays and wrapper functions for links without user-supplied event handlers.

    • Validate navigation and redirect destinations, keep ambiguous relative URLs on the current origin, and constrain prerender requests and output paths. Prevent redirect headers from appearing in serialized server function response bodies.

      Preserve native form HTTP redirects, route error handling and masks for document redirects, and per-navigation destinations for shared loader redirects. Avoid redundant origin parsing and reduce link styling and server-rendering work. Configured origins must already be normalized.

      Keep blocked-link inactive props consistent during React hydration, honor explicit redirect Location headers before checking route options, and refresh Vue link state when destinations become internal. Reuse the protocol-relative URL check while parsing redirect schemes once.

      Reduce React link bundle size by sharing pathname comparisons, state-prop selection, and element creation.

      Share normalized pathname comparisons in Solid and Vue links to reduce bundle size.

    • React Links resolve state props without temporary class-name arrays or unnecessary style copies.

    Show all 7 lines

12. 1.170.33

    6 September 2026

    Patch Changes

    • Exclude structural descendants below error and not-found boundaries from route lifecycle callbacks. Preserve lifecycle membership through invalidation, hydration, background reloads, and superseded navigation publication.

    • Preserve falsy thrown values in React and Vue error boundaries. Type React and Vue boundary error components and onCatch callbacks as unknown. Solid boundary errors remain typed as Error; SSR now wraps non-Error loader errors to match Solid’s native boundary behavior, preserving the original value in cause. Router state and loader onError values are unchanged.

      When upgrading React or Vue, narrow boundary errors (for example, with error instanceof Error) before reading message or stack. ErrorComponentProps<TError> remains available for values narrowed to a specific error type. Route onError types are unchanged.

    • Retain successful not-found matches as terminal shared boundaries during client navigation, preserving route context while the destination loads.

    Show all 10 lines

13. 1.170.32

    22 August 2026

    Patch Changes

    • preserve context during reloads

    • Updated dependencies:

      • @tanstack/router-core@1.171.27

14. 1.170.31

    19 August 2026

    Patch Changes

    • Updated dependencies:

      • @tanstack/router-core@1.171.26

15. 1.170.30

    18 August 2026

    Patch Changes

    • preserve pending UI across retained routes

    • direct export of CatchBoundary class component, remove function wrapper

    • Updated dependencies:

      • @tanstack/router-core@1.171.25

    Show all 5 lines

16. 1.170.29

    14 August 2026

    Patch Changes

    • inline isCtrlKey inside Link component for byte shaving

    • Updated dependencies:

      • @tanstack/router-core@1.171.24

17. 1.170.28

    14 August 2026

    Patch Changes

    • Avoid wrapping root components that may render the HTML document in a Suspense boundary during SSR and hydration.

    • Reuse resolved lazy route components when revisiting code-split routes, preventing unnecessary pending UI.

    • Updated dependencies:

      • @tanstack/router-core@1.171.23

    Show all 5 lines

18. 1.170.27

    12 August 2026

    Patch Changes

    • useMatchRoute w/ React Compiler

19. 1.170.26

    12 August 2026

    Patch Changes

    • Warn when an Outlet is rendered inside a pending, error, or not-found component.

    • remove the undocumented Link isTransitioning state and data-transitioning attribute

    • Apply preloadDelay to viewport link preloading and cancel pending preloads when links leave the viewport.

    Show all 6 lines

20. 1.170.25

    9 August 2026

    Patch Changes

    • Updated dependencies:

      • @tanstack/router-core@1.171.21

21. 1.170.24

    9 August 2026

    Patch Changes

    • Updated dependencies:

      • @tanstack/router-core@1.171.20

22. 1.170.23

    7 August 2026

    Patch Changes

    • bail out of Link re-renders when the resolved href and active state are unchanged

23. 1.170.22

    7 August 2026

    Patch Changes

    • retain mounted UI during revalidation

    • Updated dependencies:

      • @tanstack/router-core@1.171.19

24. 1.170.21

    6 August 2026

    Patch Changes

    • Prevent a blank frame before zero-delay initial pending UI by using a component-scoped React transition for match publication. Pending timing, boundary selection, and rendered matches continue to come from the router core.

    • createFileRoute does not rely on FileRoute class

    • clean intersection observer options in link component

    Show all 8 lines

25. 1.170.20

    5 August 2026

    Patch Changes

    • Updated dependencies:

      • @tanstack/router-core@1.171.17

26. 1.170.19

    4 August 2026

    Patch Changes

    • Rewrite match loading around a lane-based scheduler that tracks each navigation, preload, and background reload as an ordered unit of work. This fixes pending/redirect/retry state leaking between overlapping navigations, restores correct SSR status codes for redirects, errors, and not-found responses, and closes hydration gaps where the client re-ran work the server had already completed.

      • Invalidation now retires matching active preloads so older speculative loader results cannot become fresh cache data after invalidation.

      • Route headers() now only runs on the server, matching the documented behavior — it is no longer invoked during client-side asset projection.

      • The documented default gcTime and preloadGcTime now match the existing runtime default of 5 minutes (300_000).

      Removed / changed exported internals

      • RouterState no longer includes loadedAt, isTransitioning, statusCode, or redirect. Use match.updatedAt in place of loadedAt; subscribe to router.state.status / router.state.isLoading in place of isTransitioning; server response status and redirect handling are now internal to the server loader and are no longer exposed on router.state.

      • RouteMatch.fetchCount has been removed, with no replacement — it was purely informational.

      • RouteMatch.status no longer includes 'redirected' (it remains 'pending' | 'success' | 'error' | 'notFound') — redirected matches are dropped from the match list instead of being rendered.

      • RouteMatch.globalNotFound has been renamed and privatized to the internal _notFound field. Use match.status === 'notFound' instead.

      • The exported React, Solid, and Vue Match components now accept routeId instead of matchId.

      • The exported RouterStores adapter contract now uses route-keyed presentation stores: matchesId is replaced by ids, matchStores by byRoute, and getRouteMatchStore() by getMatchStore(). The separate loadedAt, isLoading, isTransitioning, statusCode, and redirect stores have been removed, along with the pending/cache stores and their setters. StoreConfig.init has also been removed. Read application-facing state from router.state; preload and cache coordination are now internal.

      • Removed RouterCore members getMatch(), updateMatch(), cancelMatch(), and cancelMatches() — read matches from router.state.matches (e.g. router.state.matches.find((m) => m.id === id)); there is no replacement for mutating or cancelling an individual in-flight match from outside the router.

      • Removed RouterCore.hasNotFoundMatch() — use router.state.matches.some((m) => m.status === 'notFound').

      • Removed RouterCore.looseRoutesById — use routesById.

      • Removed RouterCore.isPrerendering(), RouterCore.isViewTransitionTypesSupported, and RouterCore.viewTransitionPromise, with no replacement.

      • Removed RouterCore.getParsedLocationHref() and RouterCore.clearExpiredCache(), with no replacement — expired cache entries are now reconciled automatically as part of match commit.

      • Removed RouterCore.latestLoadPromise and RouterCore.beforeLoad(), with no replacement.

      • RouterCore.commitLocationPromise and RouterCore.pendingBuiltLocation have been replaced by the internal _commitPromise and _pendingLocation fields.

      • Removed the exported GetMatchFn and UpdateMatchFn types, along with the methods they typed.

      • Removed the standalone getMatchedRoutes() export from @tanstack/router-core — use the router.getMatchedRoutes() instance method instead.

      • RouterCore.loadRouteChunk() no longer accepts an array of component types as its second argument. One-argument usage is unchanged; the optional second argument is now 'errorComponent', 'notFoundComponent', or false for internal boundary loading.

      • Removed Redirect.redirectHandled, which was internal redirect bookkeeping.

      • MatchRoutesOpts.preload and MatchRoutesOpts.dest have been removed.

      • StartTransitionFn is now (fn, expected) => Promise<boolean> (previously (fn) => void). This only affects custom framework adapters that implement startTransition.

    • Updated dependencies:

      • @tanstack/router-core@1.171.16

    Show all 26 lines

27. 1.170.18

    13 July 2026

28. 1.170.17

    1 July 2026

29. 1.170.16

    16 June 2026

30. 1.170.15

    6 June 2026

31. 1.170.14

    6 June 2026

32. 1.170.13

    5 June 2026

33. 1.170.12

    5 June 2026

34. 1.170.11

    2 June 2026

35. 1.170.10

    30 May 2026

36. 1.170.9

    29 May 2026

37. 1.170.8

    24 May 2026

38. 1.170.7

    21 May 2026

39. 1.170.6

    20 May 2026

40. 1.170.5

    20 May 2026

41. 1.170.4

    17 May 2026

42. 1.170.3

    16 May 2026

43. 1.170.2

    16 May 2026

44. 1.170.1

    15 May 2026

45. 1.170.0

    15 May 2026

46. 1.169.8

    11 May 2026

47. 1.169.5

    11 May 2026

48. 1.169.2

    5 May 2026

49. 1.169.1

    1 May 2026

50. 1.169.0

    30 April 2026