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

@driggsby/deploy

v0.8.1

Published

Deploy static Driggsby apps: the deploy protocol client used by the driggsby CLI.

Readme

@driggsby/deploy

The deploy protocol client for Driggsby apps — small static web apps, each served at its own driggsby.dev address, with live data through the Driggsby SDK. Driggsby assigns every app's address at first deploy: the readable name from driggsby.json plus a unique ending, like money-dash-x7k2qf.driggsby.dev, saved back into driggsby.json.

Most people want the full CLI instead:

npx driggsby@latest login
npx driggsby@latest deploy

This package exists for two narrower uses.

One-command deploys in Node-only sandboxes

In an environment that can't run a browser sign-in but can hold a token in DRIGGSBY_TOKEN:

npx @driggsby/deploy

This reads driggsby.json in the current directory, deploys the serve folder, and makes it live. It prints two addresses: the app's page in Driggsby first, where it runs with the person's data, then the app's own driggsby.dev address, which shows no Driggsby data when opened directly. A first deploy creates the app and saves its assigned address back into driggsby.json — keep (commit) that updated file, because it is the only record of the app's address; a checkout that discards it makes the next deploy create a second app at a new address.

As a library

import {
  collectDeployFiles,
  deployProjectFiles,
  readProjectConfig,
} from "@driggsby/deploy";

const projectDirectory = process.cwd();
const config = await readProjectConfig(projectDirectory);
const collected = await collectDeployFiles(config.serveDirectory);
const { outcome } = await deployProjectFiles(
  { baseUrl: "https://app.driggsby.com", token },
  projectDirectory,
  config.slug,
  collected,
  { live: true },
);

collectDeployFiles walks the serve folder (skipping dotfiles, symlinks, node_modules, and driggsby.json), hashes every file, and enforces the deploy limits locally. deployProjectFiles offers the manifest, creates the app on first deploy (persisting the assigned slug into driggsby.json before any upload), uploads only content Driggsby doesn't already have, and finalizes the version.

Zero runtime dependencies; Node.js 18 or newer; macOS, Linux, and Windows.

License

Apache-2.0