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 🙏

© 2026 – Pkg Stats / Ryan Hefner

link-monorepos-badly

v0.3.2

Published

> Link packages from one Yarn Workspaces or Bolt monorepo to another ... sorta badly.

Readme

link-monorepos-badly

Link packages from one Yarn Workspaces or Bolt monorepo to another ... sorta badly.

Getting started

Install link-monorepos-badly globally

yarn global add link-monorepos-badly

Run an install of the foreign monorepo and the local monorepo

cd /path/to/the/foreign/monorepo
# If the foreign monorepo is using Yarn Workspaces
yarn
# If the foreign monorepo is using Bolt
bolt
cd /path/to/the/local/monorepo
# If the local monorepo is using Yarn Workspaces
yarn
# If the local monorepo is using Bolt
bolt

Link the packages from the foreign monorepo to the local monorepo

cd /path/to/the/local/monorepo
link-monorepos-badly link /path/to/the/foreign/monorepo

When you're ready to unlink packages, you can unlink the packages and reinstall.

cd /path/to/the/local/monorepo
link-monorepos-badly unlink /path/to/the/foreign/monorepo
# If the local monorepo is using Yarn Workspaces
yarn
# If the local monorepo is using Bolt
bolt

Once you've published new versions of the packages from the foreign monorepo

Terms

local monorepo

The monorepo you're linking packages to (this should be at your current working directory)

foreign monorepo

The monorepo you're linking packages from (this is the path you specify to link-monorepos-badly)

Why is this linking monorepos badly?

It's quite likely that there will be duplicated dependencies which will especially cause problems with peerDependencies. We're not attempting to solve this problem well, this is a temporary solution to the problem of linking monorepos until the Node ecosystem is compatible with Yarn PnP and we can use it to link multiple monorepos together well.