Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

SSR fetch ignores documented options and omits FetchError.response

未關閉
  • 哪裡不對？
#477 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
56/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript
領域
backend-api-design

研究方向

Start with the generated server client in packages/void/src/router/compile.ts (the issue links the relevant section) and compare its behavior with the documented options in docs/guide/typed-fetch.md and docs/reference/api/client.md. Reproduce the listed calls for both Cloudflare Workers and Node targets. Done means server-side calls honor the documented options and retries, and FetchError.response contains the HTTP response.

由索引模型根據 Issue 內容生成。

描述

fetch() from void/client accepts documented options that are silently ignored during SSR and in server-side route handlers. HTTP errors also lack the documented FetchError.response property.

This affects the generated server clients for both Cloudflare Workers and Node targets. Verified against current main at 3d7cea3, where the void package version is 1.1.11.

Reproduction

Add a delayed endpoint:

// routes/api/slow.ts
import { defineHandler } from 'void';

export const GET = defineHandler(async () => {
  await new Promise((resolve) => setTimeout(resolve, 100));
  return { ok: true };
});

Add an endpoint that always returns 503 and counts attempts:

// routes/api/unavailable.ts
import { defineHandler } from 'void';

let attempts = 0;

export const GET = defineHandler((c) =>
  c.json({ attempts: ++attempts }, 503),
);

Run these calls independently from SSR code or a server-side route handler:

import { fetch, FetchError } from 'void/client';

await fetch('/api/slow', { baseURL: '/prefix' });

await fetch('/api/slow', { signal: AbortSignal.abort() });

await fetch('/api/slow', { timeout: 10, retry: 0 });

// Restart the app before this call to reset the attempt counter.
try {
  await fetch('/api/unavailable', { retry: 2 });
} catch (error) {
  if (error instanceof FetchError) {
    console.log(error.status);
    console.log(error.data);
    console.log(error.response);
  }
}

Actual and expected behavior

Case Actual server-side behavior Expected behavior
baseURL: '/prefix' Calls /api/slow and returns { ok: true }. Uses /prefix/api/slow as the request path.
Already-aborted signal The handler still runs and returns { ok: true }. Rejects the request without running the handler.
timeout: 10 Returns the delayed response despite the deadline. Rejects when the timeout expires.
retry: 2 Calls the 503 endpoint once; error.data is { attempts: 1 }. Makes the initial attempt plus two retries before rejecting.
FetchError.response undefined, even though error.status is 503 and error.data contains the response body. Contains the HTTP Response, including status 503 and its headers.

The documented default GET retry is also absent on the server. Code using the same typed client therefore behaves differently between browser execution and SSR.

References

主要語言
TypeScript
星號
402
分支
32
平均合併
12 小時 28 分鐘
30 天內合併 PR
77

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

voidzero-dev/void 的其他 Issue

查看 voidzero-dev/void 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。