Figure out what error messages Chrome provides for various errors and make it so we have the same.
Contributor guide
Tech stack
javascriptnodejs
Domain
backenddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.jsHTTP protocolundici error handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Research Chrome's error messages for common network errors (e.g., DNS, connection, timeout). Review undici's current error handling in the source code (likely in lib/errors/ or similar). Identify discrepancies and implement updates to match Chrome's messages. Consult existing comments or linked issues for any prior discussion.
