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

@codeyam-editor/codeyam-editor

v0.1.23

Published

Language-agnostic managed execution sandbox for scenario-driven development

Readme

CodeYam Editor

A step-driven AI build editor with an isolated Live Preview, scenario capture, verification commands, and a Rust control API.

CodeYam Editor runs beside your project and drives an AI build agent through a planned, step-by-step workflow. Every feature is built together with the scenarios (the data states) that demonstrate it, shown in a live preview as you go and captured so they can be re-verified later. It works with any stack: web apps, backend services, CLIs, libraries.

Install

Recommended: the one-line installer. It installs through npm and puts codeyam-editor on your PATH:

curl -fsSL https://codeyam.com/install.sh | sh

It checks the prerequisites (Node 20 or newer, and on Linux a recent enough glibc), runs the global npm install, and adds npm's global bin directory to your shell profile, so a new shell finds codeyam-editor. It prints exactly what it changed.

Plain npm (you manage PATH yourself):

npm install -g @codeyam-editor/codeyam-editor

If you use a custom npm prefix (for example npm config set prefix ~/.npm-global to avoid sudo), add its bin directory to PATH yourself. Otherwise the install succeeds but the shell reports codeyam-editor: command not found. The one-line installer does this for you.

No install: a one-off run through npx:

npx @codeyam-editor/codeyam-editor

Requirements

  • Node.js 20 or newer.
  • One of the supported platforms. npm installs the matching native binary automatically:
    • macOS on Apple silicon (arm64) or Intel (x64)
    • Linux x64 with glibc 2.28 or newer: Ubuntu 20.04+, Debian 10+, RHEL/Rocky/Alma 8+, Fedora 29+, Amazon Linux 2023. Older distros such as CentOS 7 and Amazon Linux 2 are not supported.
    • Windows x64
  • Playwright's Chromium, for scenario screenshots: npx playwright install chromium.

Quick start

In your project directory:

codeyam-editor init     # write .codeyam/editor.json
codeyam-editor start    # start the editor and open it in your browser

start prints the editor's local URL and opens it. Pass --no-open to skip the browser, or --port <PORT> to pick the port. init --provider <claude|codex|gemini|opencode> chooses the build agent (Claude by default).

Commands

| Command | What it does | |---|---| | codeyam-editor start | Start the editor (control API and your app's process). | | codeyam-editor init | Initialize a new .codeyam/editor.json config. | | codeyam-editor mcp | Run an MCP (Model Context Protocol) server over stdio, for Claude Desktop and other MCP clients. | | codeyam-editor editor | The workflow subcommands the build agent uses: scenarios, glossary, audit, and more. |

Run codeyam-editor <command> --help for a command's options, and codeyam-editor editor --help for the full list of workflow subcommands.

Use with Claude

The editor works with Claude Code out of the box: codeyam-editor init sets up the project for it. For Claude Desktop or any other MCP client, register codeyam-editor mcp as a stdio MCP server. See codeyam.com for the other ways to install it in Claude.

Links

License

MIT. See LICENSE.