Repository navigation
Package install hang forever on placeDep for some package #55871
Description
Version
22.11.0 / 23.2.0
Platform
Linux 8bc1457235a1 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 GNU/Linux
Subsystem
Docker debian:sid-slim
What steps will reproduce the bug?
Create a docker image using
FROM debian:sid-slim:latest
ARG NODE_VERSION=22
RUN curl -fsSL https://deb.nodesource.com/setup_${NODE_VERSION}.x | bash - &&\
apt-get install -y nodejs
RUN corepack enable
Then run it and try to install yamlinc package: npm install -g --loglevel silly yamlinc
The process hang forever on this step: npm silly placeDep node_modules/yamlinc/node_modules/unset-value/node_modules/has-value isobject@2.1.0 OK for: has-value@0.3.1 want: ^2.0.0
How often does it reproduce? Is there a required condition?
Depends on which package you want to install. Some works and some others like yamlinc fail every time.
What is the expected behavior? Why is that the expected behavior?
Install the package
What do you see instead?
Process hang forever on placeDep resolution.
Additional information
Working fine on node v21.7.3 and does not seems to be linked to npm version (always 10.9.0)
Activity
avivkeller commentedon Nov 15, 2024
incorrect information@nodejs/npm
avivkeller commentedon Nov 15, 2024
(Ignoring the incorrect information above, i misunderstood the issue)
Is this only reproducible in Docker?
Bartheleway commentedon Nov 15, 2024
Yes I should have mentioned that I also tried directly one my computer and that everything was fine with node 21 & 22.
Maybe it is linked to filesystem or user permission (but I am root on docker).
aduh95 commentedon Nov 15, 2024
You should report this to npm if you're not able to reproduce without it.
Bartheleway commentedon Nov 15, 2024
So for you it is an issue related to npm package more than node even if the only difference in the scenarios is the node version?
aduh95 commentedon Nov 15, 2024
It might be caused by a bug within
node, however without a repro we cannot investigate it. If you report it to npm, they should be able to assess whether they're doing something wrong or if it is indeed a bug withnodeBartheleway commentedon Nov 18, 2024
It seems to be linked to #55602 and also as some others reported it is working fine under npm@10.8.3
The workaround for now is to add
--libc=glibcto thenpm installcommand. I hope this would help others and also that fix will soon be released.Thanks for the help.