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

which-first

v0.1.0

Published

Show which copy of a command your shell will actually run, and every other copy shadowed behind it.

Readme

which-first

Show which copy of a command your shell will actually run, and every other copy that exists but never will.

npm: C:\tools\npm.cmd
  shadowed: C:\Program Files\nodejs\npm.cmd
  shadowed: C:\Program Files\nodejs\npm.ps1

The problem it exists for

where npm lists every copy. It does not tell you which one wins, and on Windows the answer is not obvious: npm.cmd beats npm.exe because of PATHEXT, and the first directory on PATH beats all the later ones. People install a tool, run it, and get the old copy that happens to sit earlier on PATH. which-first prints the winner first and labels the rest shadowed.

Install

npm install which-first

Node 18 or newer. No dependencies.

Use

which-first npm
which-first node git python

Exit code 0 when every command resolves, 1 when one does not, 2 when you give it nothing to look up.

Resolution follows the shell: directories in PATH order, PATHEXT extensions in order, case-insensitive on Windows, repeated directories skipped. A directory that does not exist is ignored rather than reported as an error.