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

@matheusrocha89/x

v0.1.2

Published

## Motivation

Readme

X

Motivation

Nowadays we have a few options for package managers on the Frontend world. Some famous ones are npm, yarn and pnpm. Because of that, we worked on some projects that have yarn, other has pnpm, and other uses npm and it was always hard to follow which project uses what. Of course, you already passed through a situation where you were in a project that uses npm and then when you change to another project by accident you were always trying to add new dependencies using the npm CLI but the project uses yarn, and so on.

X is the command to try to solve this problem. Using x you can configure a .x-rc file with which command the project uses or let x determine which package manager to use based on the lockfile the project has.

Installation

To use x you just need to install it globally using one of the package managers (npm, pnpm or yarn):

npm:

npm install -g @matheusrocha89/x

yarn:

yarn global add @matheusrocha89/x

pnpm:

pnpm add -g @matheusrocha89/x

How to use

You can just run any command of the package manager of the project but replace the package manager name with x. For example:

Adding new dependency:

Npm:

npm install lodash

X:

x install lodash

It also accepts the flags of the package managers and forwards them to the command:

Npm installs as dev dependecy:

npm install -D lodash

X:

x install -D lodash

.x-rc

You can create a .x-rc in your project with the package manager that x should use.

For NPM:

echo "npm" >> .x-rc

For Yarn:

echo "yarn" >> .x-rc

For PNPM:

echo "pnpm" >> .x-rc