Upgrade `@tanstack/react-router` — upstream already has built-in scroll-restoration quota fix

[swear01]

What version of HAPI is running?

0.18.3

What platform is your computer?

Linux 6.17.0-1007-oracle aarch64 aarch64

What issue are you seeing?

The error still surfaces when sessionStorage quota is full:

QuotaExceedError: Failed to execute 'setItem' on 'Storage': Setting the value of 'tsr-scroll-restoration-v1_3' exceeded the quota.
HAPI depends on @tanstack/react-router@^1.143.6 (router-core@1.143.6, published 2025-12-24). That version's scroll-restoration module calls sessionStorage.setItem without try-catch, allowing the error to propagate.

The existing workaround (web/src/lib/scrollStorageGuard.ts) catches this error, but isQuotaError() only matches two error names:

err.name === 'QuotaExceedError' || err.name === 'NS_ERROR_DOM_QUOTA_REACHED'
Some browser environments may throw a different error name, causing the guard to re-throw instead of silently handling it.

What steps can reproduce the bug?

Accumulate enough session / file routes (sessionStorage cache exceeds ~5MB), then navigate between pages.

What is the expected behavior?

The QuotaExceedError should not be thrown.

Additional information

Upstream fix:

TanStack/router PR #6287 — wraps sessionStorage.setItem in try-catch, logs a warning instead of throwing.
Merged: 2026-01-05
Included from @tanstack/router-core >= 1.145.6.
This was available 4 months before HAPI issue #611 was filed (2026-05-11).
HAPI workaround:

PR #632 — scrollRestorationKey.ts (key collapsing) + scrollStorageGuard.ts (error guard), merged 2026-05-18.
The PR did not discuss upgrading the dependency; likely the upstream fix was not known at the time.
Suggestion: upgrade @tanstack/react-router to latest (currently 1.171.6) and remove the custom guard.

[github-actions]

Verified the repo state matches the dependency part of this report: web still declares @tanstack/react-router as ^1.143.6, and bun.lock resolves both @tanstack/react-router and @tanstack/router-core to 1.143.6.

The current HAPI mitigation is still active at app boot. It wraps sessionStorage.setItem, handles only the TanStack scroll-restoration storage key, and rethrows when the thrown value is not an Error named QuotaExceededError or NS_ERROR_DOM_QUOTA_REACHED. I did not find an in-repo reference to TanStack/router PR #6287, 1.145.6, or 1.171.6.

So the actionable repo-side work appears to be: evaluate upgrading TanStack Router, then decide whether scrollStorageGuard.ts can be removed or narrowed after validating scroll restoration still behaves correctly.

Relevant code:

• web/package.json:26 - declares @tanstack/react-router as ^1.143.6
• bun.lock:1044 - resolves @tanstack/react-router@1.143.6 with @tanstack/router-core: 1.143.6
• bun.lock:1048 - resolves @tanstack/router-core@1.143.6
• web/src/main.tsx:38 - installs the scroll restoration guard during bootstrap
• web/src/lib/scrollStorageGuard.ts:41 - wraps sessionStorage.setItem
• web/src/lib/scrollStorageGuard.ts:46 - rethrows non-target-key or non-quota errors
• web/src/lib/scrollStorageGuard.ts:82 - quota detection only accepts QuotaExceededError and NS_ERROR_DOM_QUOTA_REACHED
• web/src/lib/scrollRestorationKey.ts:19 - custom scroll restoration key collapsing
• web/src/router.tsx:714 - TanStack Router scroll restoration enabled with getScrollRestorationKey

---

HAPI Bot

[swear01]

Related upstream issue / PR:

• TanStack/router PR #6287 — wraps `sessionStorage.setItem in try-catch, merged 2026-01-05