interceptors: move signal handling to interceptor

Description

This issue does not include a description.

Contributor guide

Tech stack

javascriptnodejs

Domain

backendapi

Issue type

refactor

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-3 hours

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

Understanding of undici interceptorsFamiliarity with AbortSignal

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

35

Research direction

Investigate how signal handling is currently implemented in undici, likely in the core client or request handling. Move the signal related logic into a dedicated interceptor following the existing interceptor pattern. Look at existing interceptors in lib/interceptor/ for reference. The issue comments may contain guidance on expected behavior. Ensure that the new interceptor properly handles abort signals and passes them through the request pipeline.