Engineer | Lover of dogs, books, and learning | Dos XX can be most interesting man in the world, I'm happy being the luckiest. | I write about what I learn @ code-comments.com
What I've had to do is go back to whatever state has the files/folders that npm is looking for. So let's say you have a package that is on one branch and not on another, you'd have to go back to your other branch and run npm link again for that package before running npm unlink my-package-name in your main project
Also... let's say you do goof and get the
ENOENT: no such file or directory, access '/...error... then what?What I've had to do is go back to whatever state has the files/folders that npm is looking for. So let's say you have a package that is on one branch and not on another, you'd have to go back to your other branch and run
npm linkagain for that package before runningnpm unlink my-package-namein your main projectYou may also go to the folder where the symbolic link library is installed and deleted the folder.