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

@type-x/cli

v0.4.7

Published

A simple CLI runtime for installable command packages

Readme

@type-x/cli

@type-x/cli is the package behind the x binary.

Install

Install the x CLI globally:

npm install -g @type-x/cli@latest

What It Does

  • installs command packages with x add
  • runs installed commands with x <command>
  • runs local packages with x run <package-path> <command>
  • manages aliases with x alias, x aliases, and x unalias
  • scaffolds new packages with x init

Private Packages And Custom Registries

x add and x upgrade can pass npm-style registry/auth options through to the underlying npm pack call:

x add @acme/private-tool --registry https://npm.pkg.github.com --token-env GITHUB_TOKEN
x upgrade @acme/private-tool

Or pass the token directly for a one-shot install or upgrade:

x add @acme/private-tool --registry https://npm.pkg.github.com --token "$GITHUB_TOKEN"
  • --registry <url> Uses a specific npm registry for the package fetch.
  • --scope <scope> Optional override for the registry scope. Scoped package names such as @acme/private-tool are inferred automatically.
  • --token-env <ENV_NAME> Reads the auth token from an environment variable.
  • --token <value> Passes a one-shot token for the current install or upgrade only.

x upgrade reuses the package source settings from the original install. Token values are never stored.

Precedence is:

  1. current command flags
  2. stored package source metadata

Init

The scaffold is TypeScript-only.

x init my-command
x init my-command --package-name @acme/my-command --command-name hello
x init my-cli --standalone --package-name @acme/my-cli --command-name my-cli
  • default x init Creates a package meant to be consumed by x
  • x init --standalone Creates a normal npm CLI powered by @type-x/runtime

Runtime Injection

When x executes a command, it injects the runtime context from @type-x/runtime:

  • command
  • request
  • store
  • log
  • ui
  • exec
  • git
  • io
  • env

request.flags preserves repeated command flags as arrays. For example, --param a --param b is exposed to the command as request.flags.param === ["a", "b"].

Command packages can optionally configure this per command in package.json:

{
  "x": {
    "runtime": "1",
    "commands": {
      "deploy": {
        "entry": "./dist/deploy.js",
        "description": "Deploy an app",
        "runtime": {
          "repeatedFlags": "last"
        }
      }
    }
  }
}

Both runtime and runtime.repeatedFlags are optional. When omitted, repeatedFlags defaults to "array".

Store Behavior

Installed commands use the x runtime home, which defaults to ~/.type-x/type-x__cli.

Stores are shared per package, not per command. If a package exposes multiple commands, they all read and write the same package store file under ~/.type-x/type-x__cli/stores.

Internal Commands

The built-in commands are intentionally small:

  • init
  • add
  • upgrade
  • remove
  • ls
  • alias
  • aliases
  • unalias
  • run
  • doctor
  • setup-shell

Author

Iñigo Taibo