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

@cmdforge/pnpm-dlx

v0.0.3

Published

Run 'pnpm dlx <target> [options]' over npx, removing the pnpm dependency.

Readme

pnpm-dlx

Run pnpm dlx over npx, without requiring pnpm to already be installed.

Usage

npx @cmdforge/pnpm-dlx <target> [--path <package.json path>] [--registry <url>] [--] [...args]
npx @cmdforge/pnpm-dlx --from-cwd [--path <package.json path>] [--] <pnpm args...>

Example:

npx @cmdforge/pnpm-dlx github:cmdforge/tip --path package.json -- ui open https://mcp.dev.azure.com
npx @cmdforge/pnpm-dlx --from-cwd -- dlx -y tip ui open https://mcp.dev.azure.com

The CLI:

  1. Treats github:<owner>/<repo> and bare <owner>/<repo> targets as GitHub.
  2. Fetches --path directly from GitHub raw content for GitHub targets.
  3. Resolves a registry tarball URL with npm view for registry packages, using --registry or https://registry.npmjs.org by default.
  4. In --from-cwd mode, reads the requested package.json from the current working directory and runs npx pnpm@<version> <pnpm args...>.
  5. Otherwise, reads the requested remote package.json, extracts the pnpm version, then runs npx pnpm@<version> dlx -y <target> [...args].

This avoids npm pack for GitHub targets, so package lifecycle scripts do not run before the pnpm version is known.

If the requested manifest does not exist, or its packageManager is not pnpm@..., the command fails with:

pnpm not found at package/<resolved path>