Ayush SinghandZoltan Kochan b60172e3b0 fix(node-resolver): propagate network errors when reading musl assets (#14854) ...

Only HTTP 404 from unofficial-builds.nodejs.org is ignored when reading the
musl assets of a Node.js release, since that is how the mirror reports a
release it never built. Every other status and every transport error now
aborts the resolve, so a blocked or unreachable mirror can no longer leave
the musl assets out of the lockfile on one machine and not another
pnpm/pnpm#14813.

---------

Co-authored-by: Zoltan Kochan <z@kochan.io>

2026-09-14 16:24:08 +02:00

..

getNodeArtifactAddress.test.ts

…

getNodeMirror.test.ts

…

normalizeArch.test.ts

…

parseNodeSpecifier.test.ts

…

resolveNodeRuntime.test.ts

…

resolveNodeVersion.test.ts

…

resolveNodeVersions.test.ts

…

tsconfig.json

…