Homebrew npm install: could not symlink

node.jsNpmHomebrew

node.js Problem Overview


So I made the mistake of trying to get rid of all sudo dependencies. I downloaded npm as a package from the site and did a manual/global install. But it seemed as if i was always having to run with sudo...so I tried to uninstall and run with homebrew.

Now I can't get node or npm to even run...I guess I have to link with brew link them but i'm getting this error:

Could not symlink share/doc/node/gdbinit
Target /usr/local/share/doc/node/gdbinit
already exists. You may want to remove it:
  rm '/usr/local/share/doc/node/gdbinit'

I've tried removing that: And i've gotten permission denied.

I have tried running brew prune. I have tried to uninstall then reinstall using these steps:

$ brew uninstall npm
$ brew uninstall node
$ npm uninstall npm -g
$ sudo rm -rf /usr/local/lib/node_module

https://stackoverflow.com/questions/12607155/error-the-brew-link-step-did-not-complete-successfully

I am running Yosemite 10.10.5. I have git version 2.6.0 installed. My homebrew is updated. A brew doctor gives me this warning:

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
    node

Not sure where to go from here. I'm trying to lose my reliance on CodeKit and get gulp up and running.

node.js Solutions


Solution 1 - node.js

It looks like several files and directories in /usr/local are now owned by root, since you ran a couple of steps using sudo. To get rid of these, take back ownership of all of the files and directories under /usr/local:

sudo chown -R $(whoami) $(brew --prefix)/*

Once that is done, run brew doctor again.

Similar questions can be found here:

Solution 2 - node.js

In my case, I was continue to execute command brew link node and upon every execution, it is keep on saying to remove some files. I just followed the instructions and keep on removing them with sudo. At last, after 5 such removals, I have the linking done.

enter image description here

Solution 3 - node.js

Had something similar happen with node listed as an unlinked keg. This is what worked for me on MacOS Big Sur:

  1. sudo mkdir -p /usr/local/sbin // had issues with sbin, ignore if you don't.
  2. sudo chown -R $(whoami) /usr/local/sbin // ignore if sbin isn't an issue.
  3. brew link --overwrite node
  4. brew cleanup // wanted to be sure this alone ran fine :)
  5. brew doctor // found un brewed header files, but not concerned about those.
  6. node -v // checking node version
  7. npm -v // checking npm version

If the above doesn't work, try starting from scratch and seeing if these steps help:

  1. brew uninstall node
  2. brew update
  3. brew upgrade
  4. brew cleanup
  5. brew install node
  6. sudo chown -R $(whoami) /usr/local
  7. brew link --overwrite node
  8. brew postinstall node

You can definitely chain these commands and make the input way shorter, but small victories help ease some of the frustration, while also making it easier to ID exactly what step failed, rather than displaying a chained-command error and having the person rage (╯°□°)╯︵ ┻━┻ because they are now even more lost lol.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionpwhittView Question on Stackoverflow
Solution 1 - node.jsnwinklerView Answer on Stackoverflow
Solution 2 - node.jsAshishView Answer on Stackoverflow
Solution 3 - node.jsJesseView Answer on Stackoverflow