New LTS 20.9.0 uses npm 10.1.0 which has issues with proxy config

[lscorcia]

Version

v20.8.1

Platform

Linux 4f5c14380cd5 5.4.0-165-generic #182-Ubuntu SMP Mon Oct 2 19:43:28 UTC 2023 x86_64 GNU/Linux

Subsystem

npm

What steps will reproduce the bug?

$docker run --rm -it node:20 /bin/bash
root@4f5c14380cd5:/# npm --version
10.1.0

Also see https://github.com/nodejs/node/tree/v20.9.0/deps . The latest commit for npm clearly states that npm 10.1.0 is used.

How often does it reproduce? Is there a required condition?

100% reproducible

What is the expected behavior? Why is that the expected behavior?

npm 10.1.0 is affected by regression npm/cli#6835 , already fixed in npm 10.2.0. We use only node LTS for our CI/CD pipelines. Also, our company requires a proxy to access all external resources. Since LTS switched from 18 to 20, all builds fail. Node LTS v20 should ship with a working version of npm.

What do you see instead?

Node LTS v20 ships with a broken npm package. Since it does not pick up the proxy settings, we can't even update it inside the container as it does not reach the registry.

Additional information

No response

[mhdawson]

@nodejs/npm

[mhdawson]

There is already a PR to update in main here - #50258

[lscorcia]

Main already uses npm 10.2.0 which fixes the proxy problem. This issue is about the 20.9.0 release. npm >= 10.2.x should be backported in the 20.9.x LTS release line.

[lukekarrys]

npm 10.2.0 landed in main here: #50027

I believe the next Node 20 release will include an update to npm@10.2.0 (or 10.2.1 if #50258 lands before that).

We can keep this issue open until that is released, but I don't believe there is any work to do here.

[silverwind]

node v20.10.0 was released with npm v10.2.3.

[lscorcia]

I can confirm the issue is solved by updating to the latest LTS.