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

devsandboxes

v0.6.0

Published

Manage devcontainer-style sandboxes on docker, podman, or Apple container, from the CLI or a typed Node API.

Readme

devsandboxes

Manage devcontainer-style sandboxes on docker, podman, or Apple container: many throwaway instances per repo from one devsandboxes.toml. This package ships the native devsandbox binary (Linux x64/arm64, macOS arm64, Windows x64) plus a typed Node API.

The package installs a devsandbox command (npm i -g devsandboxes); npx devsandboxes runs it without installing.

Config reference and concepts: github.com/Nemikolh/devsandboxes.

CLI

npx devsandboxes            # dashboard (on a TTY)
npx devsandboxes run web    # start an instance of [sandbox.web]
npx devsandboxes exec -it web zsh

Node API

import { spawn } from 'node:child_process';
import * as devsandbox from 'devsandboxes';

const { name, worktree } = await devsandbox.run('web', { dir: './sandboxes', stderr: 'inherit' });
const { instances } = await devsandbox.status({ dir: './sandboxes' });
for (const i of instances) console.log(i.name, i.status.state, i.drift);

const { exitCode, stdout } = await devsandbox.exec(name, ['git', 'status']);

// Your own process or pty (node-pty takes the same file/args): a login shell.
const { file, args } = devsandbox.execArgv(name, [], { interactive: true, tty: true });
spawn(file, args, { stdio: 'inherit' });

await devsandbox.rm(name, { deleteBranch: true });

| Function | Resolves to | | ------------------------------------------ | ------------------------------------ | | status() | Snapshot (sandboxes, instances, services) | | ls() / ps({ all }) / stats() | SandboxRow[] / ContainerRow[] / StatsRow[] | | service.ls() | ServiceRow[] | | inspect(name) | runtime inspect document (unknown) | | run(sandbox, { name, branch, base }) | RunRecord (name, container, workspace, folder, worktree, branch) | | start / stop / rebuild(name \| { all: true }) | void | | rm(name, { deleteBranch, force }) / rename(a, b) / gc() / service.rebuild(name) | void | | logs(name, { lines }) | log text | | exec(name, argv, { input }) | { exitCode, stdout, stderr } (never rejects on exit code) | | execArgv(name, argv?, { tty, interactive }) | { file, args } to spawn yourself (sync; no argv: login shell) | | cli(args) | raw { exitCode, stdout, stderr } |

Every function takes { dir, cwd, env, signal, stderr }, except the synchronous binaryPath() and execArgv(). dir is the config root (-C). A failed command rejects with DevsandboxError (exitCode, stdout, stderr).

rm never prompts: deleteBranch: true deletes the worktree branch run created (git branch -D, unmerged commits too); false or omitted keeps it. Branches run reused are always kept. It rejects, removing nothing, when the worktree has uncommitted or untracked changes, unless force: true: that discards them, and a step that fails is skipped with a warning on stderr so the instance is still removed.

Platforms

The binary comes from an optional dependency (@devsandboxes/<platform>-<arch>), so don't install with --omit=optional. On other platforms, cargo install devsandbox and point DEVSANDBOX_BINARY at the result.