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

@dsherret/which

v0.7.4

Published

Finds the path to the specified command.

Readme

deno-which

JSR npm

Finds the path to the specified command. Works in Deno and Node.js.

# Deno
> deno add @david/which

# Node.js
> npm install @dsherret/which
import { which, whichSync } from "@dsherret/which";

const pathToCurl = await which("curl");

Custom Environment

If you want to use this with an fake or in memory environment, then you can provide a custom environment as the second parameter.

For example:

const pathToCurl = await which("curl", {
  isWindows: true,
  async stat(filePath: string): Promise<{ isFile: boolean }> {
    // implement this
  },
  statSync(filePath: string): { isFile: boolean } {
    // implement this
  },
  // lstat/readLink are used as a fallback on Windows when stat throws
  // with EACCES, to resolve Windows Store app execution aliases (and
  // user-created symlinks pointing at them)
  async lstat(
    filePath: string,
  ): Promise<{ isFile: boolean; isSymlink: boolean }> {
    // implement this
  },
  lstatSync(filePath: string): { isFile: boolean; isSymlink: boolean } {
    // implement this
  },
  async readLink(filePath: string): Promise<string> {
    // implement this
  },
  readLinkSync(filePath: string): string {
    // implement this
  },
  env(key: string): string | undefined {
    // implement getting an environment variable
  },
  // optional method for requesting broader permissions for a folder
  requestPermission(folderPath: string): void {
    Deno.permissions.requestSync({
      name: "read",
      path: folderPath,
    });
  },
});