This is a
playground to test code. It runs a full
Node.js environment and already has all of
npm’s 400,000 packages pre-installed, including
fix-yarn-global-packages with all
npm packages installed. Try it out:
fix-yarn-global-packages lists no main file and has no index.js, so it can't be directly required. If this is a mistake, please let us know. It may however contain internal files that you can require manually:
This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.
Installed global packages using
Can't access them since updating
fix-yarn-global-packages to use your global packages again!
$ npm install -g fix-yarn-global-packages
Make sure to use
yarn. That way next time you update
node you'll still be able to run this tool.
If you can't run your global packages after updating
node just run the following in your terminal:
$ fix-yarn-global-packages linked http-server linked css-beautify linked http-beautify linked js-beautify linked <all your other global packages>
With any luck, you should be able to use your yarn-installed global packages again.
My recommendation is that you install global packages using npm until the issue is resolved.
You can still use
yarn to install global packages in the mean time - it just means you'll have to run
fix-yarn-global-packages each time.
npm symlinks global package binaries to
yarn symlinks global package binaries to the same directory that
The issue is when
node is updated using tools such as
Rather than clobbering the old version of
brew stores the updated version of node in a new directory.
The problem is that all the existing symlinked binaries are in the old
yarn global bin
Essentially it's copying what yarn did when you first ran
yarn global add <blah>