-
Notifications
You must be signed in to change notification settings - Fork 3k
npm unlink does not unlink from global path #4005
Comments
unlink is just an alias for uninstall, ala the unix unlink. |
So how would you undo the npm link then? (Outside of digging up the symlink
|
You can |
good enough for me |
This seems very unintuitive. |
Exactly, @mzgol. |
Reopening this, as I agree that this is a confusing inconsistency in the CLI, but be forewarned that it's very low priority and won't be happening for a while. Also you can stop +1ing it now, thanks. |
...actually, @isaacs put together a patch to make |
Fixed in 7bf85cc. Thanks for your patience, everybody. |
I don't know if this is the best place to raise this, but here goes: The NPM Link documentation provides an example of how to link a package:
But it doesn't show you how to unlink a package. May I suggest adding the following?
|
This isn't working for me. I created a package locally and linked it globally for testing, now I cannot unlink it. I've tried
and But if I
I can still see that |
@rohan-deshpande i'm seeing the same thing. I'm on windows, so npm unlink is not removing from Very unexpected after calling |
Post how to link & unlink scoped packages, which work for me on mac at least. May it helps someone. Link scoped pakcages:
Unlink scoped packages:
|
I also have the same Issue when using npm link. I also use: when using npm unlink, the symlink doesn't get removed from the specified alias of nodejs. Even after switching the nodejs via nvm, the error still occurs. Haven't figured out yet, which file i need to delete. Some errors of that: |
I had some packages npm linked before. |
Steps to reproduce:
The expected result is to have the project no longer linked globally but alas, unlink says that the project is not installed under its own node_modules folder (and yes, indeed it is not) and doesn't unlink it globally.
The text was updated successfully, but these errors were encountered: