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

@mrrobot0985/create-devcontainer

v0.8.6

Published

Instantiate devcontainer templates from the mrrobot0985 collection into any workspace

Readme

Full documentation is available in the template repository docs.

@mrrobot0985/create-devcontainer

npm version CI License: MIT

Instantiate devcontainer templates from the mrrobot0985/devcontainer-templates collection into any workspace.

Usage

npx @mrrobot0985/create-devcontainer <template-id> [target-folder]

Examples

Apply the minimal Ollama + Claude CLI template to the current directory:

npx @mrrobot0985/create-devcontainer ollama-claude-cli .

Apply the studio template to a specific project:

npx @mrrobot0985/create-devcontainer ollama-claude-cli-studio ./my-project

Apply the minimal template with a custom devcontainer name:

npx @mrrobot0985/create-devcontainer ollama-claude-cli ./my-project --name "My Project"

Apply a template and generate a README.md skeleton:

npx @mrrobot0985/create-devcontainer ollama-claude-cli ./my-project --readme

Combine --name and --readme to create a named devcontainer and a matching README title:

npx @mrrobot0985/create-devcontainer ollama-claude-cli ./my-project --name "My Project" --readme

Templates

Source of truth in this monorepo ships 15 templates in four portfolio layers. What you get via npx depends on the published npm version (see the badge above). If monorepo package.json is ahead of npm, use a local build or wait for a release (templates#83).

Full details: Template Catalog.

Layer A — Claude + Ollama

| ID | Name | | --------------------------- | ----------------------------- | | ollama-claude-cli | Ollama + Claude CLI | | ollama-claude-cli-cpu | Ollama + Claude CLI (CPU) | | ollama-claude-cli-compose | Ollama + Claude CLI (Compose) | | ollama-claude-cli-python | Ollama + Claude CLI + Python | | ollama-claude-cli-studio | Ollama + Claude CLI Studio |

Layer B — Agent entry points

| ID | Name | | ----------------------- | --------------------- | | grok-build-cli | Grok Build CLI | | grok-build-cli-studio | Grok Build CLI Studio | | pi-coding-agent | Pi Coding Agent | | hermes-agent | Hermes Agent | | codex-cli | OpenAI Codex CLI | | gemini-cli | Google Gemini CLI | | opencode-cli | OpenCode CLI |

Layer C — Multi-agent evaluation

| ID | Name | | -------------- | ---------------------- | | multi-ai-cli | Multi-AI CLI Workspace |

Layer D — Domain stacks

| ID | Name | | ------------------------ | --------------------------- | | cloud-native-k8s | Cloud Native Kubernetes | | data-engineering-spark | Data Engineering with Spark |

Run create-devcontainer with no arguments to see the full list (grouped by layer).

Options

| Flag | Description | | ------------ | -------------------------------------------------------- | | --registry | Force GHCR registry mode (default is bundled local copy) | | --force | Overwrite an existing .devcontainer directory | | --name | Override the devcontainer configuration name | | --readme | Create a README.md skeleton in the target directory | | --help | Show help | | --version | Show version |

Development

Run from the repo source:

cd packages/create-devcontainer
npm install
npx tsx src/index.ts ollama-claude-cli ../../test-output

Build and test:

npm run build
npm test

Template Sync Check

The hard-coded template registry must stay in sync with src/ in the repo root. If you add, remove, or rename a template, regenerate the registry:

npx tsx scripts/sync-template-registry.ts --write

CI and the pre-commit hook validate this automatically and fail if they drift.