Correct Cloudflare network error detection

[timkelty]

PR #10 copied Cloudflare's unpunctuated documentation label into the existing TypeError message set. Workerd instead constructs Error("Network connection lost.") for disconnections.

This replaces the mistaken matcher with the actual runtime shape and updates the type guard to Error.

Workerd source · Workerd test

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-29T17:17:54.597189Z	74dbb3d	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[sindresorhus]

This error appears to be Workerd’s generic representation for any DISCONNECTED exception, not something specific to Fetch. That means we cannot reliably distinguish a Fetch network error from binding, socket, stream, or Durable Object failures.

The Fetch standard requires network failures to reject with a TypeError, so I think the correct fix belongs in Workerd rather than broadening this package’s contract based on a generic error message.

[timkelty]

Fair enough. I'll post an update here when I open one in workerd.

[timkelty]

Opened cloudflare/workerd#7195 with a current workerd repro and the Fetch spec requirement: cloudflare/workerd#7195

FWIW - with this realization, you might consider removing the current CF workers check for clarity. Even if workerd starts throwing TypeError, it looks like the check is missing the trailing . and wouldn't match.