0
Fork 0
mirror of https://github.com/TanStack/router.git synced 2026-11-16 19:38:07 +00:00
Commit graph

3,291 commits

Author SHA1 Message Date
Brandon Roberts
9ba9b9468c chore: fixed build 2025-09-26 18:19:03 -05:00
Brandon Roberts
02318dd86d chore: fix build 2025-09-26 18:18:19 -05:00
Chau
ecb1d71593 test: wip 2025-09-26 18:18:12 -05:00
Chau
a84ad62b31 feat: separate angular devtools 2025-09-26 18:18:06 -05:00
Chau
1415281c6d chore: make sure angular examples work 2025-09-26 18:17:57 -05:00
Chau
3dd515d226 fix: type issue 2025-09-26 18:17:15 -05:00
Chau
9fa3e87775 chore: adjust example with latest angular router impl 2025-09-26 18:17:15 -05:00
Chau
f097f4163c chore: adjust code styles; lint 2025-09-26 18:17:15 -05:00
Brandon Roberts
391e9d8a64 chore: use ng-packagr for the build 2025-09-26 18:17:13 -05:00
Brandon Roberts
3f936d8ef5 chore: fix package exports paths 2025-09-26 18:17:09 -05:00
Brandon Roberts
8b324894a8 feat: introduce @tanstack/angular-router package 2025-09-26 18:17:07 -05:00
Manuel Schiller
87875da6b2 fix: server function types with request middleware installed
fixes #5238
2025-09-27 01:15:18 +02:00
Magnus May
2ff5bc20f7
docs: add Bun production server guide for TanStack Start (#5237)
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Manuel Schiller <manuel.schiller@caligano.de>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2025-09-27 01:01:49 +02:00
Tanner Linsley
e55b436969 release: v1.132.10 2025-09-26 19:08:05 +00:00
Paweł Błaszczyk
e46ba71cb9
fix: add StartInstance re-export which is used as a return type from createStart (#5259)
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2025-09-26 21:02:21 +02:00
Tanner Linsley
0babe5d805 release: v1.132.9 2025-09-26 03:57:47 +00:00
James Opstad
716cc05c7b
fix: Add optimizeDeps.entries for client and ssr environments (#5223)
Co-authored-by: Manuel Schiller <manuel.schiller@caligano.de>
2025-09-26 05:52:14 +02:00
Tanner Linsley
2e7cb7ffa8 release: v1.132.8 2025-09-26 03:33:53 +00:00
Manuel Schiller
f9bf3363d8
fix: compile createMiddleware using start-compiler-plugin (#5245) 2025-09-26 05:32:15 +02:00
Tanner Linsley
8219466eee release: v1.132.7 2025-09-25 15:30:09 +00:00
Manuel Schiller
e6ef21809c
fix: opt into SSR type level serializability check (#5233)
default `false` was not working for plain router

fixes #5222
2025-09-25 17:28:40 +02:00
Tanner Linsley
86aa74e345 release: v1.132.6 2025-09-25 03:01:51 +00:00
Brooke Holmes
98a02d77b6
fix(router-core): avoid infinite serializer recursion for arrays (#5199)
Fixes some issues I was having with https://conform.guide (also fixes
https://github.com/TanStack/router/issues/4533)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Compile-time serialization validation now recognizes readonly arrays
and tuples for inputs and results, preserving tuple shapes and improving
type inference and editor experience; no runtime changes.

* **Tests**
* Added type-level tests covering recursive, nested, readonly array and
tuple scenarios to verify compile-time validation and type propagation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-09-25 04:55:33 +02:00
Tanner Linsley
49e5fad4ea release: v1.132.5 2025-09-24 20:41:09 +00:00
Manuel Schiller
5c6eed67ce fix: exclude start and router from optimizeDeps for solid as well 2025-09-24 22:33:11 +02:00
Tanner Linsley
9d3bbbd812 release: v1.132.4 2025-09-24 20:24:21 +00:00
Manuel Schiller
c7213749df fix: export fake startInstance 2025-09-24 22:18:27 +02:00
Tanner Linsley
956d5f27e0 release: v1.132.3 2025-09-24 19:45:30 +00:00
Manuel Schiller
e4d5671ba9
fix: various fixes (#5215)
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2025-09-24 21:42:56 +02:00
Tanner Linsley
c2f732d30f release: v1.132.2 2025-09-23 22:38:18 +00:00
Manuel Schiller
bd5557613a
fix: deps (#5195) 2025-09-24 00:33:48 +02:00
John Colvin
0aa36667e5
Fix typo in error message for server rendering (#5161) 2025-09-24 00:28:41 +02:00
Tanner Linsley
f5ac86a045 release: v1.132.1 2025-09-23 21:40:21 +00:00
autofix-ci[bot]
ba84c91df5
ci: apply automated fixes 2025-09-23 21:34:36 +00:00
Manuel Schiller
6f87bc8dcd fix: correctly handle undefined serializationAdapters 2025-09-23 23:33:12 +02:00
Tanner Linsley
a5909a45ab release: v1.132.0 2025-09-23 17:36:29 +00:00
Manuel Schiller
32faee22da
feat: Start RC (#5189)
Co-authored-by: Nico Lynzaad <nlynzaad@zylangroup.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Tanner Linsley <tannerlinsley@users.noreply.github.com>
Co-authored-by: James Opstad <13586373+jamesopstad@users.noreply.github.com>
Co-authored-by: chorobin <chrishorobin@hotmail.com>
Co-authored-by: Tanner Linsley <tannerlinsley@gmail.com>
Co-authored-by: Nico Lynzaad <44094871+nlynzaad@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: hokkyss <hokkyss2@gmail.com>
Co-authored-by: Philippe Serhal <philippe.serhal@gmail.com>
Co-authored-by: Jack Herrington <jherr@pobox.com>
Co-authored-by: Brenley Dueck <brenleydueck@gmail.com>
2025-09-23 11:34:54 -06:00
Tanner Linsley
4a6dcd09cf release: v1.131.50 2025-09-22 01:13:50 +00:00
Nico Lynzaad
ecd79d2b63
fix(router-core): Non nested paths - only strip trailing underscore on route segments (#5182)
as part of #5169 we made changes to strip underscores from the paths to
ensure it is dealt with correctly during parsing.

inadvertently this stripped it from not only the route segments but also
the base segments. This PR resolves that issue by making
`baseParsePathName` aware which type of segments it is parsing.

a new optional boolean paramater, ```basePathValues```, is introduced in
`baseParsePathName` and `parsePathname` to allow this distinction
between routeSegments and/or basesegments to be passed on to
`baseParsePathName`.

2 new functions are introduced `parseBasePathSegments` and
`parseRoutePathSegments`, which is just wrapper functions around
`parsePathname`, but ensures clearer understanding of what set of
parsing instructions is applied and `basePathValues `is set correctly
based on the requirement.

updated the unit tests to take into account the need not to strip the
base values and also enhanced the e2e tests as well to ensure more
through testing with different usages.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- New Features
- Added non-nested route demos (named, prefix, suffix, path) with
index/foo/bar pages and updated navigation in React and Solid examples.
- Bug Fixes
- Improved path parsing/matching to handle non-nested segments,
prefixes/suffixes and trailing underscores; refined route
sorting/resolution.
- Tests
- Added comprehensive E2E coverage for non-nested paths; removed
obsolete baz-based tests.
- Expanded unit tests for path interpolation and matching (underscore,
prefix/suffix cases).
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-09-22 03:12:27 +02:00
Tanner Linsley
0d00f2862a release: v1.131.49 2025-09-19 23:36:55 +00:00
Manuel Schiller
1d5c5f7776
fix: tell router that rendering finished when rendering to string (#5174)
fixes #5155

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Improved server-side rendering stability by correctly finalizing the
initial render before injecting additional HTML, preventing rare hangs
or incomplete pages.
  * Applies to both React and Solid router SSR paths.

* **Performance**
* Slightly reduces SSR latency by signaling render completion earlier in
the pipeline.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-09-20 01:34:03 +02:00
Tanner Linsley
f5872dfef7 release: v1.131.48 2025-09-18 23:06:58 +00:00
Nico Lynzaad
cf2346ba42
fix(router-core): Non-nested paths (#5169)
This PR continues on from #5165 and primarily adds additional tests to
path resolution and matchByPath for non-nested paths in additiona to e2e
test for both react and solid router to verify non-nesting
functionality.

One additional issue was picked up for handling of normal path segments.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- New Features
- Added non-nested demo routes and navigation examples (including
dynamic and edit paths) for React and Solid, with headings, links, and
parameter displays.
- Bug Fixes
- Improved path parsing/decoding for non-nested segments to prevent
unintended nesting and ensure correct parameter values.
- Tests
- Added broad unit tests for non-nested path parsing/matching/resolution
(case-sensitive/insensitive, wildcards, optional/fuzzy).
- Added e2e tests validating non-nested navigation and params; reduced
e2e flakiness by awaiting network idle.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-09-19 01:05:26 +02:00
Tanner Linsley
3b69de0f41 release: v1.131.47 2025-09-18 18:29:36 +00:00
Nico Lynzaad
ab12c06634
fix(router-core): parse non-nested path params correctly (#5165)
When parsing path params to interpolate the path non-nested path params
```/path/$param_``` was being parsed in the same manner as regular path
params ```/path/$param```.

This PR adds consideration for the trailing underscore when parsing the
path for non-nested path params as well as unit tests on path
interpolation and e2e tests for useParams to ensure this is parsed
correctly and updates correctly when params change.

This resolves #5164

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- New Features
- Support trailing-underscore non-nested path params (e.g., /users/$id_
→ /users/123).
- UI shows an additional navigation link for the non-nested route
(/params-ps/non-nested/foo2/bar2) and improved link display text.

- Tests
- Expanded React and Solid e2e tests to cover the new link, navigation,
and param parsing for foo2/bar2.
- Added unit tests validating interpolation/matching for the $param_
syntax.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-09-18 20:28:01 +02:00
Tanner Linsley
a8714cdb15 release: v1.131.46 2025-09-18 18:16:05 +00:00
wookhyung
b0ea8de91d
fix(router): prevent script tag duplication in SSR and client-side navigation (#5095)
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2025-09-18 20:09:15 +02:00
Lee
2c8d5ce61e
fix(router): respect target attribute on inner component (#5115) 2025-09-18 20:06:37 +02:00
Tanner Linsley
d49b20459c release: v1.131.45 2025-09-18 17:31:08 +00:00
Flo
c77dbc34f7
refactor(react-router): Link component composeHandler performance (#5168)
I noticed a slight performance dip during some navigations and the
bottom-up call list of the flame graph seemed to point to the
`composeHandler`. This seems (surprising and) pretty minor, but I'm
measuring a consistent 3ms self-time when the resulting handler is
actually being called.

This PR proposes ditching array methods and using a `for-of` loop. This
is good-enough™ and preserves the generality and DX of this function for
a 25% perf improvement.

```sh
 ✓  @tanstack/react-router  tests/foo.bench.tsx > composeHandlers 10064ms
     name                      hz     min     max    mean     p75     p99    p995    p999     rme   samples
   · array methods  37,152,711.10  0.0000  0.1624  0.0000  0.0000  0.0000  0.0000  0.0002  ±0.14%  18576357
   · for-of         47,029,751.81  0.0000  0.0236  0.0000  0.0000  0.0000  0.0000  0.0001  ±0.07%  23514876   fastest

 BENCH  Summary

   @tanstack/react-router  for-of - tests/foo.bench.tsx > composeHandlers
    1.27x faster than array methods
```

A slightly more performant (~30%) version would be to handle *exactly* 2
handlers instead of an arbitrary number (since `composeHandlers` is only
used w/ 2 callbacks) but this does affect the generality and DX of this
function.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Refactor**
- Updated link event handling to short-circuit when an action is
prevented, maintaining existing behavior.
- Streamlined internal logic for handling user interactions with links
for improved efficiency.
- **Performance**
- Minor efficiency improvements in link interaction handling without
altering the public API or user-facing behavior.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-09-18 19:29:39 +02:00