QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value ...'

[xiaoyutx94]

What version of HAPI is running?

0.18.4

What platform is your computer?

x64

What issue are you seeing?

http://localhost:18080

browser -> F12 -> console log

QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value of 'tsr-scroll-restoration-v1_3' exceeded the quota. at Object.set (index-AeIQePZT.js:10:94090) at Object.fn (index-AeIQePZT.js:10:96498) at index-AeIQePZT.js:10:112128 at Set.forEach (<anonymous>) at W_.emit (index-AeIQePZT.js:10:112092) at ref (index-AeIQePZT.js:10:146225) at Dc (index-AeIQePZT.js:9:93924) at b4 (index-AeIQePZT.js:9:98301) at Zs (index-AeIQePZT.js:9:106605) at b4 (index-AeIQePZT.js:9:97693)

What steps can reproduce the bug?

Open a new session

What is the expected behavior?

No response

Additional information

No response

[github-actions]

This matches TanStack Router scroll restoration writing tsr-scroll-restoration-v1_3 into sessionStorage and hitting the browser storage quota.

I verified that 0.18.4 already has a guard for this cache, but it only handles quota errors that are actual Error instances. The current main branch has a follow-up fix after the v0.18.4 tag that handles this more broadly and also resets TanStack's in-memory scroll cache when storage remains too large. So this looks like a known issue that is fixed on main, but not yet present in the latest tagged release shown in this repo.

Relevant code:

• web/src/lib/scrollStorageGuard.ts:11 - defines the exact storage key from the console error: tsr-scroll-restoration-v1_3.
• web/src/lib/scrollStorageGuard.ts:89 - wraps sessionStorage.setItem and handles failed writes for that key.
• web/src/lib/scrollStorageGuard.ts:113 - resets the persisted scroll state when the value cannot be pruned safely.
• web/src/lib/scrollStorageGuard.ts:118 - syncs TanStack's in-memory scroll cache after pruning.
• web/src/main.tsx:38 - installs the scroll restoration guard during web app bootstrap.
• web/src/lib/scrollRestorationKey.ts:9 - explains the root cause: default history-entry keys can grow the scroll cache until sessionStorage quota is exceeded.

---

HAPI Bot