Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

`npm rm -g $(npm ls)` removed /usr/lib #2293

Closed
fbstj opened this Issue Mar 22, 2012 · 4 comments

Comments

Projects
None yet
2 participants

fbstj commented Mar 22, 2012

I only have what was already running left before my system dies completely I think.

Owner

isaacs commented Mar 22, 2012

That's kind of weird. npm ls outputs a tree and a bunch of stuff. It looks like the first line is the root path, though, and the path.resolve() goes up to the root.

Yeah. That sure is a ghastly bug, nevertheless. npm uninstall / could be disastrous.

@isaacs isaacs closed this in b57d3bb Mar 22, 2012

fbstj commented Mar 23, 2012

Thanks, goes and reinstalls his system

isaacs added a commit to isaacs/node-v0.x-archive that referenced this issue Mar 23, 2012

2012.03.22 Version 0.6.14 (stable)
* net: don't crash when queued write fails (Igor Zinkovsky)

* sunos: Fix EMFILE on process.memoryUsage() (Bryan Cantrill)

* crypto: fix compile-time error with openssl 0.9.7e (Ben Noordhuis)

* unix: ignore ECONNABORTED errors from accept() (Ben Noordhuis)

* Add UV_ENOSPC and mappings to it (Bert Belder)

* http-parser: Fix response body is not read (koichik)

* Upgrade npm to 1.1.12
  - upgrade node-gyp to 0.3.7
  - work around AV-locked directories on Windows
  - Fix npm/npm#2293 Don't try to 'uninstall' /
  - Exclude symbolic links from packages.
  - Fix npm/npm#2275 Spurious 'unresolvable cycle' error.
  - Exclude/include dot files as if they were normal files
Owner

isaacs commented Mar 23, 2012

Jeez, I'm so sorry, again. That really sucks.

fbstj commented Mar 24, 2012

heh, no worries mate :D npm is awesome, and I enjoy reinstalling things XD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment