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

nhx

v0.0.3

Published

Node.js Hybrid eXecutor (a `uvx` inspired tool)

Readme

nhx - Node.js Hybrid eXecutor (a uvx inspired tool)

npm version npm downloads

A hybrid of node ./script.js and npx package - run scripts or packages with automatic dependency handling.

npm install -g nhx

Why nhx?

  • Self-contained scripts - Scripts declare their own dependencies and just work
  • No project setup - No package.json, no npm install, no node_modules
  • Share scripts easily - Send a single file that anyone can run
  • Fast - Dependencies are cached globally, subsequent runs are instant
  • Works offline - Once cached, no network needed

Options

--with <dep>       Add a dependency (repeatable, supports @version)
--engine <spec>    Node version (e.g. node:18, node:>=16)
--run-postinstall  Allow postinstall scripts (disabled by default)
-h, --help         Show help

All other flags pass through to node.

Examples

# Run an npm package
nhx cowsay hello

# Run a local script (dependencies installed automatically)
nhx ./script.js

# Add a dependency for a script
nhx --with=lodash ./script.js

# Pin a specific version
nhx [email protected] ./script.js

# Use a specific node version
nhx --engine=node:18 ./script.js

# Pipe from stdin
curl -s https://example.com/script.js | nhx -

# All node flags work
nhx -e 'console.log(1)'
nhx --check ./script.js

Self-contained scripts

Scripts can declare their own dependencies inline:

// hello.mjs
/*/ // <package>
{ dependencies: { chalk: "^5.0.0" } }
/*/ // </package>

import chalk from 'chalk';
console.log(chalk.green('Hello!'));
nhx ./hello.mjs

Dependencies are installed automatically on first run and cached for future runs.

Specifying a node version

/*/ // <package>
{ engines: { node: ">=18 <21" } }
/*/ // </package>

console.log(process.version);

If your current node satisfies the range, it's used directly. Otherwise nhx downloads an appropriate version.

Loaders

Use tsx as a declared dependency and as a loader:

#!/usr/bin/env -S nhx --with=tsx --import tsx
import { something } from './other.ts';

You can also do that with inline dependencies:

#!/usr/bin/env -S nhx --import tsx
/*/ // <package>
{ devDependencies: { tsx: "^4" } }
/*/ // </package>

License

MIT