Michaël Zasso comments

Results 1686 comments of


                                            Michaël Zasso

SLR returns NaN when inputs and outputs are 1-element arrays

Hello @jobo322, do you have an opinion on this issue?

TypeError: first argument must be a positive number

We would gladly accept a pull request to fix this :)

Enable debug information for `fetch()` via `NODE_DEBUG=http`

@nodejs/undici wdyt?

Memory leak with native fetch on Node v19+

Can you try running `node` with for example `--max-old-space-size=128`? If there is a real memory leak, the process should crash when used memory reaches around 128MB.

native `fetch` api does not respect `keepalive` parameter in `RequestInit`

`keepalive` is `false` by default, and it has nothing to do with the `connection: keep-alive` header. See https://fetch.spec.whatwg.org/#request-keepalive-flag > request . [keepalive](https://fetch.spec.whatwg.org/#dom-request-keepalive) Returns a boolean indicating whether or not request...

Default fetch timeout too short

You can make Node.js fetch use a custom dispatcher with: ```js globalThis[Symbol.for('undici.globalDispatcher.1')] = dispatcher; ```

fix: use readable-stream

What about this: ```diff diff --git a/package.json b/package.json index a02ae10..222a235 100644 --- a/package.json +++ b/package.json @@ -41,7 +41,8 @@ "docs" ], "scripts": { - "build:node": "npx [email protected] index-fetch.js --bundle --platform=node...

Michaël Zasso

SLR returns NaN when inputs and outputs are 1-element arrays

TypeError: first argument must be a positive number

Enable debug information for `fetch()` via `NODE_DEBUG=http`

Memory leak with native fetch on Node v19+

native `fetch` api does not respect `keepalive` parameter in `RequestInit`

Default fetch timeout too short

fix: use readable-stream

fix: use readable-stream

sequential.test-watch-mode-inspect seems flaky

build, tools: copy release assets to staging R2 bucket once built