Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Complete Remix 3 server error handling

未关闭
#24,664 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@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
平均合并
1 天 16 小时
30 天内合并 PR
576

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

getsentry/sentry-javascript 的其他 Issue

查看 getsentry/sentry-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。