v16.18.0 breaks npm ci

[damianprzygodzki]

Version

v16.18.0

Platform

Ubuntu 20.04.5 LTS

Subsystem

No response

What steps will reproduce the bug?

Execute npm ci or npm i

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

No response

What is the expected behavior?

Before an update (16.17.1) everything installed well, there is some issue as after update i can't install deps by npm.

What do you see instead?

npm ERR! code EPIPE
npm ERR! syscall write
npm ERR! errno -32
npm ERR! write EPIPE

Additional information

No response

[bnoordhuis]

EPIPE means the connection was severed.

Given that v16.18.0 has been out for a few days now, it seems unlikely that it's a regression in node; otherwise we would have received many more reports by now.

Chances are it's something on your end. Things you can try:

• run on another system, see what happens
• go back to v16.17.1, see what happens
• check if node (not npm) can connect to the outside world
• and so on

[bnoordhuis]

That said, it's possible you're hitting #44992, which is npm bug npm/cli#5278. If that's the case you should head over to npm and close this issue.

[frank-dspeed]

@bnoordhuis i guess the most that hit #44992 will use the workaround supplyed which is

git@github.com:<name>.....

needs to be changed to

git@github.com/<name>

so replacing

: with / 

Will do the trick its not a real bug it is only a bad parser implementation i did not look into blame

Can u use that without update?

Yes you can apply the workaround it will stay working and call it a day.

[lukekarrys]

Closed by npm/cli#5761

[ccl2of4]

Hello,

I am currently experiencing this issue on any version of node after 16.18.0. I have tried the latest versions from both the 16 and 18 release channels.

Using git bisect and building node from source, I have narrowed down the problematic commit to

5f406a3a53: http: reuse socket only when it is drained (3 months ago) <ywave620>. (associated pull request 43902)

When I run npm ci on any branch which includes this commit, I encounter this EPIPE error. If I revert the commit and rebuild node, I can see from the logs that the EPIPE error is still emitted, but it is handled properly.

Unfortunately, I'm really not sure what exactly it is about my environment that is causing this EPIPE error, as it doesn't seem like it's affecting very many users at all. The best I can currently do is attach a set of detailed logs.

For each of these sets of logs, I ran DEBUG='*' NODE_DEBUG='*' npm ci

• v16.17.1 (Working version)
• v16.18.0 (First released broken version)
• v16.19.0 (Latest release on v16 LTS branch)

To quickly find the error in these logs, just search for the string 'EPIPE'. In summary, it looks like in v16.17.1, EPIPE is emitted but handled; in later versions EPIPE is emitted but is unhandled.

Please let me know if there's any further information I can provide for troubleshooting.