SSR crash on Vercel: "object is not iterable" in handleServerRoutes after upgrading to [email protected] ([email protected])

Đang mở
#8,584 3 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
28/100
Loại issue
Lỗi
Độ rõ ràng
Cần làm rõ
Mức độ hoạt động
Sôi nổi
Lĩnh vực
backend, web-dev

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

information needed
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
  1. Deploy a TanStack Start app to Vercel using the vercel nitro preset (Node.js runtime) with @tanstack/[email protected].
  2. Request / (or any SSR page) from the deployed production URL.
  3. 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.x runtime), nitro preset vercel
  • 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)

Ngôn ngữ chính
TypeScript
Star
15.3k
Fork
1.9k
Merge trung bình
1 ngày 5 giờ
Pull request đã merge (30 ngày)
46

Chuẩn bị môi trường

Mở trong Codespaces

Khởi chạy dev container của dự án ngay trên trình duyệt, bằng tài khoản GitHub của bạn.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của TanStack/router

Tất cả issue của TanStack/router

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.