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

@rcompat/args

v0.11.0

Published

Standard library program arguments

Readme

@rcompat/args

Runtime-agnostic access to command-line arguments.

What is @rcompat/args?

A cross-runtime module that provides consistent access to program arguments across Node, Deno, and Bun. Write your CLI tools once and run them on any JavaScript runtime.

Installation

npm install @rcompat/args

Usage

import args from "@rcompat/args";

// args is a string[] containing your program arguments
console.log(args);

Running node app.js foo bar --verbose will output

[ 'foo', 'bar', '--verbose' ]

Example: Simple CLI

import args from "@rcompat/args";

const [command, ...rest] = args;

switch (command) {
    case "greet":
        console.log(`Hello, ${rest[0] ?? "world"}!`);
        break;

    case "help":
        console.log(
            `Usage:
  app.js <command> [args]

Commands:
  greet [name]   Greet the specified name (or 'world')
  help           Show this help message`
        );
        break;

    default:
        console.log("Usage: app.js <command> [args]");
}
node app.js greet Bob # Hello, Bob!
bun app.js greet      # Hello, world!

How It Works

Different runtimes expose command-line arguments differently:

| Runtime | Source | Includes runtime/script? | | ------- | -------------- | ------------------------ | | Node | process.argv | Yes (first two elements) | | Bun | Bun.argv | Yes (first two elements) | | Deno | Deno.args | No |

@rcompat/args normalizes this by always returning only your program's arguments — the runtime executable and script path are stripped away.

The package uses runtime keys to select the appropriate implementation at import time, with zero runtime overhead.

Cross-Runtime Compatibility

| Runtime | Supported | | ------- | --------- | | Node.js | ✓ | | Deno | ✓ | | Bun | ✓ |

No configuration required — just import and use.

License

MIT

Contributing

See CONTRIBUTING.md in the repository root.