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

@spawn-dock/cli

v1.0.76

Published

Minimal Vite-powered TypeScript console starter using Effect

Downloads

1,108

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ilyar.softwareilyar.softwareglazlkglazlk

Keywords

effecttypescriptviteconsole

Readme

spawn-dock

spawn-dock creates a separate Docker environment for each repository, issue, or PR. By default, projects reside in ~/.spawn-dock.

Prerequisites

  • Docker Engine or Docker Desktop
  • Docker access without sudo
  • Node.js and npm

Installation

npm i -g @spawn-dock/cli
spawn-dock --help

Authentication

spawn-dock auth github login --web
spawn-dock auth codex login --web
spawn-dock auth claude login --web

Example

You can pass a link to a repository, branch (/tree/...), issue, or PR.

spawn-dock clone https://github.com/SpawnDock/cli/issues/122 --force --mcp-playwright
  • --force recreates the environment and removes the project's volumes.
  • --mcp-playwright enables Playwright MCP and the Chromium sidecar for browser automation.

Automatic agent launch:

spawn-dock clone https://github.com/SpawnDock/cli/issues/122 --force --auto
  • --auto selects Claude or Codex based on available authentication. If both are available, the choice is random.
  • --auto=claude or --auto=codex forces a specific agent.
  • In auto mode the agent executes the task on its own, creates a PR, and the container is cleaned up after completion.

Details

spawn-dock --help

SpawnDock CLI

This workspace also includes a separate package @spawn-dock/cli for bootstrapped SpawnDock TMA projects.

It runs inside a directory that already contains spawndock.config.json and defaults to launching opencode. The runtime can be overridden via SPAWNDOCK_AGENT_RUNTIME=codex|claude|opencode or via agentRuntime in spawndock.config.json.

This is an intentionally minimal launcher. It locks the project root and launches the agent only from it; opencode by default starts via codex sandbox linux, and codex itself launches with workspace-write sandbox.