npm rm -g <linked module> results in removing stuff inside the link #8891

Closed
iarna opened this Issue Jul 10, 2015 · 1 comment

Projects

None yet

1 participant

@iarna
Member
iarna commented Jul 10, 2015

It should just remove the symlink. Instead it looks INSIDE the symlink and deletes that. As npm's make publish does this, it kind of results in npm committing suicide. This is not desirable.

@iarna iarna added the bug label Jul 10, 2015
@iarna iarna added this to the 3.1.2 milestone Jul 10, 2015
@iarna iarna added a commit that referenced this issue Jul 17, 2015
@iarna iarna install: Move computation of the _location field to a more appropriat…
…e place

PR-URL: #8977
Fixes: #8891
3120c75
@iarna iarna added a commit that referenced this issue Jul 17, 2015
@iarna iarna install: Move computation of the _location field to a more appropriat…
…e place

PR-URL: #8977
Fixes: #8891
9a98482
@iarna iarna added a commit that referenced this issue Jul 17, 2015
@iarna iarna install: Move computation of the _location field to a more appropriat…
…e place

PR-URL: #8977
Fixes: #8891
96ce660
@iarna iarna added a commit that referenced this issue Jul 17, 2015
@iarna iarna install: Move computation of the _location field to a more appropriat…
…e place

PR-URL: #8977
Fixes: #8891
56531f7
@iarna iarna added a commit that referenced this issue Jul 17, 2015
@iarna iarna install: Move computation of the _location field to a more appropriat…
…e place

PR-URL: #8977
Fixes: #8891
233c3d3
@iarna iarna added a commit that referenced this issue Jul 18, 2015
@iarna iarna install: Move computation of the _location field to a more appropriat…
…e place

PR-URL: #8977
Fixes: #8891
d914557
@iarna iarna added a commit that referenced this issue Jul 18, 2015
@iarna iarna install: Move computation of the _location field to a more appropriat…
…e place

PR-URL: #8977
Fixes: #8891
59bb0d7
@iarna
Member
iarna commented Jul 20, 2015

The fix for this landed in master with 59bb0d7 and in 3.1.3.

@iarna iarna closed this Jul 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment