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

@profullstack/cli

v0.2.0

Published

The commands every Profullstack CLI shares: `update` and `uninstall`, done the same way the tool was installed (curl installer, npm, bun, pnpm or yarn). No dependencies.

Readme

@profullstack/cli

The commands every Profullstack CLI shares, so no tool writes them twice:

mytool update            # update, the same way it was installed
mytool update --check    # only say whether a newer version exists
mytool uninstall         # remove it (asks first; --yes to skip; alias: remove)

It looks at where the running copy really lives and picks the matching tool:

| Installed with | update runs | uninstall runs | | --- | --- | --- | | our curl installer (and w3bs install) | the installer again, with your flags | <prefix>/share/<name>/uninstall.sh | | npm i -g | npm install -g pkg@latest | npm uninstall -g pkg | | bun add -g | bun add -g pkg@latest | bun remove -g pkg | | pnpm add -g | pnpm add -g pkg@latest | pnpm remove -g pkg | | yarn global add | yarn global add pkg@latest | yarn global remove pkg |

A copy it cannot place (a project's node_modules, a source checkout) is never touched: it prints the command to run instead. update checks the registry or a configured version feed before running an installer, skips an equal version, and refuses to downgrade. If the feed is unavailable or malformed, it stops without reinstalling. --force reinstalls only when the installed version is not newer.

Install an hourly per-user update check from an installer after the CLI wrapper is in place:

import { installAutoUpdate } from "@profullstack/cli/auto-update";

await installAutoUpdate({ name: "readm3", command: "/home/me/.local/bin/readm3" });

The updater uses systemd user timers or cron on Linux, launchd on macOS, and Task Scheduler on Windows. It runs readm3 update --quiet; removing a CLI can call removeAutoUpdate(name) to remove its scheduled check.

Use

import { lifecycle, lifecycleUsage } from "@profullstack/cli";

export async function main(argv = process.argv.slice(2)) {
  if (await lifecycle(argv, {
    name: "readm3",                              // command, and <prefix>/share/<name>
    package: "@profullstack/readm3",
    version: VERSION,                            // the running version
    installer: "https://readm3.com/install.sh",  // optional curl installer
    installerCommand: "update",                 // pass `update` to the install script
    installerArgs: () => desktopInstalled() ? ["--desktop"] : [], // flags to keep on update
  })) return;
  // ...the tool's own commands
}

lifecycle returns false for any other command, sets process.exitCode on failure, and refuses to uninstall without a terminal unless --yes is given. Put lifecycleUsage(name) in your --help.

For a version feed outside npm, pass latestVersion: () => fetchVersion(url). Also exported: detectInstall, lifecycleCommand, latestVersion, fetchVersion, compareVersions. The @profullstack/cli/auto-update entry exports installAutoUpdate, removeAutoUpdate, and autoUpdatePaths.

No dependencies. Node 18+ and Bun. MIT.