#Yarn install webpack globally install

#Yarn install webpack globally install

Looks like we’ve got to remove all our global modules and install them all over again, or possibly move the symlinks. It doesn’t seem a great solution though, does it? It seems like we still have an architectural/organisational issue here: Yarn is installing symlinks to global binaries in a particular version of Node’s folder. What happens when we upgrade Node and Homebrew instead points its symlink to new folder /usr/local/Cellar/node/7.7.4? This should work (when you open a new terminal). PATH = / usr / local / Cellar / node / 7.7.3 / bin : $ PATH One way around this would be to add that path to our PATH variable in our ~/.profile file which runs when we open a terminal:

Now we have a problem: this location is not checked by the system and your global packages are not going to be found! That’s where the node binary is located and that’s where Yarn is going to install your global packages. The symlink is found and it runs Node which might actually be located in, for example, /usr/local/Cellar/node/7.7.3.

Homebrew keeps previous versions of software in its “Cellar” and it inserts a symlink to the version to run (usually the latest) into your usr/local/bin instead. If you installed Node with its installer and the binary itself was put straight into your /usr/local/bin folder, things are going to work fine: that location is in your PATH and sought by the shell, so the symlinks to your global package binaries will also be found there and executed as expected.īut if you installed Node using Homebrew (and I recommended installing any system software via Homebrew where possible) then it’s a different story.