You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
Imho. it should actually be run in a docker container matrix: all the official https://hub.docker.com/_/node/ images and for each: both a version where the source folder is part of the container and one where it is a virtual folder.
docker run -i -t node /bin/bash
#then paste this in or create costum node image
cd $(npm root -g)/npm \
&& npm install fs-extra \
&& sed -i -e s/graceful-fs/fs-extra/ -e s/fs\.rename/fs.move/ ./lib/utils/rename.js \
# run your command again all works
npm install -g npm
We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.
If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.
For more information about our new issue aging policies and why we've instituted them please see our blog post.
I'm opening this issue because:
What's going wrong?
There is a bug when trying to update packages using npm inside a docker container.
How can the CLI team reproduce the problem?
docker run -i -t node /bin/bash
npm install -g npm
This result in the following error:
What's the feature?
I suggest a Docker container be added to the Continuous Integration environments, to catch these kinds of issues sooner.
I'd argue that having npm be tested inside a Docker container is easily as important as testing on Windows.
Is this a feature you're prepared to implement, with support from the npm CLI team?
Sure thing.
The text was updated successfully, but these errors were encountered: