SSR crash on Vercel: "object is not iterable" in handleServerRoutes after upgrading to [email protected] ([email protected])
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 28/100
- issue の種類
- バグ
- 明瞭さ
- 説明が足りない
- 活発さ
- 活発
- 技術スタック
- node.js, react, typescript
調査の方向性
Start with packages/router-core/src/ssr/handlerCallback.ts, server-functions-handler.ts, and ServerFunctionSerializationAdapter.ts, then compare the built Vercel function under .vercel/output/functions/__server.func/index.mjs across the working and failing versions. Reproduce on Vercel with the reported runtime context and trace the SSR response contract until the source of the iterable error is identified; done means SSR requests render successfully on the security-fixed release.
索引モデルが issue の本文から書いたものです。
説明
Describe the bug
After upgrading to the latest patched release of @tanstack/react-start (1.168.60, pulling in @tanstack/[email protected] and @tanstack/[email protected]), our app crashes on every SSR request to / when deployed to Vercel (Node.js runtime, nodejs24.x, nitro vercel preset), with:
TypeError: object is not iterable (cannot read property Symbol(Symbol.iterator))
at handleServerRoutes (file:///var/task/_ssr/server-<hash>.mjs:1528:49)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
This reproduces consistently on real Vercel infrastructure (confirmed via Vercel's own runtime error/log aggregation across multiple separate deployments of the identical commit), but we have not been able to reproduce it by invoking the exact same built .vercel/output/functions/__server.func/index.mjs bundle directly in a plain Node 24 process (both GET / and HEAD / against a bare new Request(...) return 200 locally, full HTML). So whatever triggers it depends on something specific to the real request/runtime context Vercel provides (headers, the context object with a real waitUntil, etc.) that we haven't been able to pin down yet from the outside.
Suspected cause
We noticed @tanstack/[email protected] was released together with #8573 ("fix(start): align server function transport behavior"), which tightened normalizeSsrResponse/isSsrResponse in packages/router-core/src/ssr/handlerCallback.ts to throw (Expected a Response from the SSR handler) instead of silently passing through non-Response values, and reshaped the server-function result contract (result.error/result.result) in server-functions-handler.ts and ServerFunctionSerializationAdapter.ts. We suspect something in our app's SSR path produces a value that no longer satisfies the new, stricter contract, and that whatever is swallowing/transforming that TypeError ends up presenting it as "object is not iterable" rather than the new explicit error message — but we haven't fully traced it through the minified bundle yet.
Your Example Website or App
Not shareable (private production app), sorry — happy to provide more detail/log excerpts on request.
Steps to Reproduce the Bug or Issue
- Deploy a TanStack Start app to Vercel using the
vercelnitro preset (Node.js runtime) with@tanstack/[email protected]. - Request
/(or any SSR page) from the deployed production URL. - Observe a 500 with the stack trace above.
We were unable to reduce this to a minimal public repro yet since it doesn't reproduce outside real Vercel infrastructure in our testing — will update if we manage to isolate it further or narrow down which of our server functions/middleware triggers it.
Expected behavior
SSR request to / should render normally, as it did on @tanstack/[email protected] (pre-upgrade).
Screenshots or Videos
No response
Platform
- OS: Vercel (Linux,
nodejs24.xruntime), nitro presetvercel - Browser: N/A (server-side crash)
Additional context
Versions involved: @tanstack/[email protected], @tanstack/[email protected], @tanstack/[email protected], @tanstack/[email protected], @tanstack/[email protected], @tanstack/[email protected], @tanstack/[email protected].
We upgraded specifically to pick up the fix for the recent critical XSS advisory in @tanstack/react-start (GHSA-qx66-fv34-fjm8 / CVE-2026-102989), so we can't simply stay on the older version. Since 1.168.60 is currently the only released version carrying that security fix, this regression is currently blocking us from deploying it — we've had to roll back to the pre-CVE-fix version in production in the meantime.
tanstack/router version
1.168.60 (react-start) / 1.171.34 (router-core) / 1.169.39 (start-server-core)
Platform
Vercel (Node.js 24.x runtime, nitro vercel preset)
- 主要言語
- TypeScript
- スター
- 15.3k
- フォーク
- 1.9k
- 平均マージ
- 1日 5時間
- マージ済み PR(30日)
- 46
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
TanStack/router のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
Masked navigation drops the first character of the hash each time (__tempLocation hash missing '#')対応中かも @hassanabrar202 が 8 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
router-generator: lazy-load Prettier (costs ~300–450ms per build even when formatting is off)対応中かも @Sheraff が 27 日前に担当しました。 オープンpackage: router-generator performance
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
router-generator: sibling `physical()` subtrees in a virtual route config generate duplicate identifiers対応中かも @Sheraff が 27 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
docs(router): clarify static title fallback in SPA mode対応中かも @Rohan-Dedhia が 17 日前に担当しました。 オープン
難易度 1/5 1〜3時間 初心者へのやさしさ 62/100
メンテナーはふだん 1 日以内に返信
TanStack/router の issue をすべて見る
似ている issue
-
[BUG]: Shared links drop the configured basePath on GitHub Pages対応中かも @anshulchikhale30-p が今日担当しました。 オープンbug
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Add: GTrekkerオープンcheck:passed streams:add
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
メンテナーはふだん 1 日以内に返信
-
area: ui Bug Payload OSS
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
payloadcms/payload#19839 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
jeanibarz/knowledge-base-mcp-server#1291 ·
メンテナーはふだん 1 日以内に返信