undici icon indicating copy to clipboard operation
undici copied to clipboard

An HTTP/1.1 client, written from scratch for Node.js

Results 379 undici issues
Sort by recently updated
recently updated
newest added

### Version v20.2.0 ### Platform ``` Darwin Kamils-MacBook-Pro.local 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000 arm64 ``` ### Subsystem _No response_ ### What steps will...

## Bug Description The change introduced by 3c514d8d98b3887db165b0ace3014a9c6ad0dfb9 removes the ability to reproduce the wasi-sdk sources from the Node.js deliverables. ## Reproducible By In Fedora, we require that all of...

bug

## This would solve... It would simplify for me, as a plain old user, to not have to import node-fetch when node supposedly should have a "native" version of fetch...

enhancement

### Version 18.16.0 ### Platform Microsoft Windows NT 10.0.19044.0 x64 ### Subsystem No response ### What steps will reproduce the bug? ```node fetch("http://localhost", { keepalive: false }) ``` ### How...

Docs

The fetch spec requires us to create a new web Readable stream for every `Response` and `Request` object, which can likely be avoided in most cases. Given the following examples:...

good first issue

This PR implements a multipart/form-data parser with a 1:1 match to busboy's API. This took me about a week to complete and many, many hours. I believe docs and types...

## Bug Description Running benchmarks on Node v20.1.0 fails. ## Reproducible By Upgrade Node.js to 20.1.0 if haven't already Run `npm run bench` inside the undici repo ## Expected Behavior...

bug

By default fetch times out after 30 seconds. This causes issues like https://github.com/nodejs/undici/issues/1248 Chrome has 300 second time out. Please set default unidici fetch timeout to 300 seconds by default.

enhancement
good first issue

## Bug Description I've noticed a bug where if the body of a fetch response is large (let us say above 50mb), grabbing the body contents takes a long time...

bug

## Bug Description Something node-fetch and browser could handle was the infamous raw deflate response from old servers basically if the coding is either: `coding === 'deflate' || coding ===...

enhancement
good first issue