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

Complete Remix 3 server error handling

未關閉
#24,664 1 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@chargome 已經在處理了。

開始於 2026年9月23日。

評估

這個 Issue 還沒有評估資料。

描述

Remix

Cover the error paths the router middleware alone does not see, and stop reporting things that are not faults.

  • Patch createRequestListener in @remix-run/node-fetch-server and install an onError that chains to the app's own. This is the only thing covering an app whose fetch handler does not use fetch-router.
  • Skip aborted requests. raceRequestAbort rejects with the request's abort reason when a client disconnects, so without this every user navigating away mid request creates an issue.
  • Add a shouldHandleError option on the integration, following the @sentry/hono convention: skip 3xx and 4xx errors carrying a numeric status, capture the rest.

No de-duplication needed when a failure is seen by both the middleware and onError. captureException already marks the value __sentry_captured__ and drops the second report.

A handler returning a 500 response is not an error. Nothing is thrown, so no issue is created and the status lands on the span.

Done when e2e covers the abort case and the non-router handler case. The abort test must fail if the guard is removed.

主要語言
TypeScript
星號
8.7k
分支
1.9k
平均合併
2 天 10 分鐘
30 天內合併 PR
560

環境準備

從這裡開始

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

getsentry/sentry-javascript 的其他 Issue

查看 getsentry/sentry-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

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

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