Skip to content

Fix blog route matching article header #769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Sheraff wants to merge 6 commits into
base: main
Choose a base branch
from
+3 −1
Open

Fix blog route matching article header #769

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2058dab
chore: update @tanstack/* dependencies
actions-user Feb 8, 2026
c1d0ffa
fix(blog): route matching article header to fit new layout
Sheraff Mar 17, 2026
d660019
Merge branch 'main' into fix-blog-route-matching-article-header
Sheraff Mar 17, 2026
7f80431
ci: apply automated fixes
autofix-ci[bot] Mar 17, 2026
6166e18
fix lockfile
Sheraff Mar 17, 2026
6964b7c
fix lockfile
Sheraff Mar 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added public/blog-assets/tanstack-router-route-matching-tree-rewrite/big-number.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified public/blog-assets/tanstack-router-route-matching-tree-rewrite/header.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 3 additions & 1 deletion src/blog/tanstack-router-route-matching-tree-rewrite.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,12 @@ authors:
- Florian Pellet
---

![Big performance number](/blog-assets/tanstack-router-route-matching-tree-rewrite/header.png)
![Header](/blog-assets/tanstack-router-route-matching-tree-rewrite/header.png)
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reduce hero image payload in route-matching blog post

The new top-of-article image points to header.png, which in this commit is a 3,391,000-byte PNG (public/blog-assets/tanstack-router-route-matching-tree-rewrite/header.png), roughly 100× larger than the previous header asset. Because this image is rendered at the start of the post, every reader pays this transfer cost up front, which will noticeably hurt page load/LCP on slower networks; please resize/compress or switch to a more efficient format before using it as the header.

Useful? React with 👍 / 👎.

Copy link

@coderabbitai coderabbitai bot Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Use meaningful alt text (or empty alt if decorative).

On Line 9, Header is too generic for screen readers. Please either provide descriptive alt text (e.g., “Fantasy landscape illustration used as the article header”) or make it decorative with empty alt text (![](...)).

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@src/blog/tanstack-router-route-matching-tree-rewrite.md` at line 9, The image
markdown currently uses a generic alt text "Header" in the line containing
"![Header](/blog-assets/tanstack-router-route-matching-tree-rewrite/header.png)";
replace that alt text with a meaningful description (e.g., "Fantasy landscape
illustration used as the article header") or make it decorative by using an
empty alt (`![](/blog-assets/.../header.png)`), updating the markdown line
accordingly so screen readers receive either the descriptive text or treat the
image as decorative.


We achieved a 20,000× performance improvement in route matching in TanStack Router. Let's be honest, this is _definitely_ cherry-picked, but the number is real and comes from a real production application. More importantly, it shows that matching a pathname to a route is no longer bottlenecked by the number of routes in your application.

![Big performance number](/blog-assets/tanstack-router-route-matching-tree-rewrite/big-number.png)

## The Real Problem: correctness, not speed

One big responsibility of a router is to match a given URL pathname (e.g., `/users/123`) to a route definition (e.g., `/users/$userId`). This is deceptively complex when you consider all the different types of route segments (static, dynamic, optional, wildcard) and the priority rules that govern which route should match first.
Expand Down
Loading