nodejs/undici

Error messages

Closed

#942 opened on Aug 12, 2021

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)JavaScript (444 forks)batch import
enhancementfetchgood first issue

Repository metrics

Stars
 (5,319 stars)
PR merge metrics
 (Avg merge 2d 10h) (82 merged PRs in 30d)

Description

Figure out what error messages Chrome provides for various errors and make it so we have the same.

Contributor guide

Research direction
Investigate the error messages that Chrome returns for various HTTP errors (e.g., connection refused, timeout, DNS failure) and compare them to the current error messages in undici. Then implement missing error messages to match Chrome's behavior.
Tech stack
javascriptnodejs
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Node.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70