Closed merceyz closed 7 months ago
Worth noting: nock just added support for fetch
in their last beta release: https://github.com/nock/nock/pull/2580
@aduh95 any suggestions for how to debug the Windows issue?
I've tried storing body as a Buffer and Uint8Array and it throws Unable to deserialize cloned data
for both and I can't reproduce it locally.
I was able to reproduce the ci failure on my machine. This patch fixed it for me: 0001-Use-ArrayBuffer-instead-of-Uint8Array.patch
I can confirm @stduhpf findings :+1:
Unable to deserialize cloned data
again, quite weird..
Yeah, I already tried using an ArrayBuffer
and the Map
shouldn't be a problem since it worked when body
was a string, but it was worth a try.
Yeah but what’s weird is that we were able to reproduce the failure of https://github.com/nodejs/corepack/pull/365/commits/064345669de97413e106cb84141d3180c47fbe0f but on later commits, the tests pass locally with NOCK_ENV=replay
🤷♂️
@aduh95 @stduhpf since you're able to reproduce the issue locally could you make a bug report upstream to Node.js and/or v8?
Changes Corepack to use the built-in
fetch
and theProxyAgent
from Undici.Since
fetch
supports compressed responses by default the bandwidth used when fetching fromhttps://repo.yarnpkg.com/tags
is also reduced (Transferred 1.71 kB (5.46 kB size)
.Closes https://github.com/nodejs/corepack/pull/361 FIxes https://github.com/nodejs/corepack/issues/293
BREAKING CHANGE: Corepack is now using the built-in
fetch
method and theProxyAgent
from Undici to perform requests, setups using custom registries and/or proxies might be affected.