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

youmightnotneed

v0.3.0

Published

Find the CSS, HTML, or Web API that replaces your JavaScript dependencies.

Readme

youmightnotneed

Find the CSS, HTML, or Web API that replaces your JavaScript dependencies. The same catalog runs at youmightnotneed.dev.

npx youmightnotneed

npx works whether or not the package is installed. It resolves a local node_modules/.bin copy first. The bare youmightnotneed command only works after a global install.

Reads the nearest package.json and prints what the platform now covers, grouped by how well supported the replacement is.

npx youmightnotneed [path] [options]

  path            A package.json, or a directory holding one.
  -p, --package   Check one npm package by name instead of reading a
                  package.json. Use it before you install something.
  -r, --rule      Print one rule in full by its id, including the conditions
                  and the shapes people hand-roll instead. Use it when you are
                  holding code rather than a package name.
  -v, --verbose   Print every condition where the dependency still wins.
      --json      Machine-readable output, with provenance for the data.
      --no-color  Disable colour. NO_COLOR is respected too.
  -h, --help      Show help.
      --version   Print the version.

Before adding a dependency, check whether the platform already covers it:

npx youmightnotneed --package axios --verbose

Run it with --verbose before you change anything. The conditions are the point: a dependency in package.json is not proof of what it is used for, so every finding is a "this may apply", and the report says when it does not.

Powered by @jomae/catalog. MIT.