npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

fix-yarn-global-packages

v1.0.1

Published

Use this to fix your yarn global packages after upgrading node

Downloads

5

Readme

fix-yarn-global-packages

Installed global packages using yarn?

Can't access them since updating node?

Use fix-yarn-global-packages to use your global packages again!

Installation

$ npm install -g fix-yarn-global-packages

Make sure to use npm over yarn. That way next time you update node you'll still be able to run this tool.

Usage

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.

What now?

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.

Why does yarn break my global packages?

npm symlinks global package binaries to /usr/local/bin.

yarn symlinks global package binaries to the same directory that node lives.

The issue is when node is updated using tools such as brew.

Rather than clobbering the old version of node, brew stores the updated version of node in a new directory.

The problem is that all the existing symlinked binaries are in the old node directory.

What does fix-yarn-global-packages do under the hood?

  • Finds all the files in ~/.config/yarn/global/node_modules/.bin
  • symlinks each of the files above into yarn global bin

Essentially it's copying what yarn did when you first ran yarn global add <blah>