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

create-reactor-app

v2.2.0

Published

Scaffold a real-time AI video app with the Reactor SDK in seconds. Starter templates for Helios and other world models — run `npx create-reactor-app`.

Readme

Create Reactor App

🧩 Create Reactor App is a CLI tool that helps you quickly bootstrap a new application using the Reactor SDK. Get started with interactive AI applications in seconds!

Quick Start

npx create-reactor-app my-app --model=helios

Or with pnpm:

pnpm dlx create-reactor-app my-app --model=helios

Usage

npx create-reactor-app [project-name] --model=<name> [options]

The model argument is required. If you omit the project name, you will be prompted for it interactively.

Arguments:

| Argument | Description | | -------------- | --------------------------------------------------- | | project-name | Name of the project to create (prompted if omitted) |

Options:

| Option | Description | | --------------- | ----------------------------------------------------- | | --model, -m | Model to scaffold a project for (required) | | --token, -t | GitHub token for private repository access (optional) | | --help, -h | Show help message |

Examples:

# Project name first, model flag after
npx create-reactor-app my-app --model=helios

# Flag first, project name after
npx create-reactor-app --model=lingbot my-app

# Project name omitted — you will be prompted for it
npx create-reactor-app --model=helios

# With a GitHub token (only needed if the template repo is private)
npx create-reactor-app my-app --model=helios --token ghp_xxxxxxxxxxxx

Available Models

Templates live in templates/ in this repository — one runnable Next.js app per model Reactor serves on the API. By default the model name maps 1:1 to a folder of the same name (e.g. --model=helios clones the templates/helios/ folder), so a folder name there is a public identifier and renaming one breaks the CLI.

The CLI also supports an optional alias map (MODEL_MAP in bin/create-reactor-app.ts) for cases where the public model name needs to differ from the folder name. It is empty by default — add an entry only when you want a name → folder rename.

Run the CLI without --model to see the list of available models in the templates repo. The output lists explicit aliases first (with the resolved folder shown after →) and then any remaining unmapped folders.

Private Repository Access

While this repository is private, npx create-reactor-app cannot read the template list or clone anonymously, so it prompts for a GitHub token. Pass --token (or -t) to skip the prompt. Once the repository is public the token is no longer needed and both paths work unauthenticated.

Getting Started After Creation

After creating your project:

cd your-project-name
pnpm dev

Open http://localhost:3000 in your browser to see your application running. Make sure to setup your API keys first!

Templates

Every template lives in templates/, which has its own README covering what each one demonstrates, the auth model they all share, and the one behaviour of @reactor-team/js-sdk 3.x that is easy to get wrong. Each folder also carries a skill/SKILL.md written for someone extending it.

The CLI resolves templates from this repository's default branch, not from the installed package, so a template fix reaches users as soon as it merges — no release required. A change to the CLI itself still needs a release.

Documentation

For comprehensive guides, API references, and tutorials, visit the official Reactor documentation:

📚 Reactor Documentation

Requirements

  • Node.js 16 or later
  • pnpm (recommended) or npm

Local Development

To test or develop the CLI locally:

# Install dependencies
pnpm install

# Build the CLI
pnpm build

# Link it globally
pnpm link --global

Now you can use create-reactor-app anywhere on your system:

create-reactor-app my-app

To unlink when you're done:

pnpm unlink --global

Releasing

Publishing to npm is automatic: bump version in package.json, merge to main, then create a GitHub Release tagging that version. The publish workflow builds and runs npm publish for you via npm's trusted publishing (OIDC) — no token to manage. It no-ops if that version is already on the registry, so re-running a release is always safe.

License

Apache 2.0 © 2024-2026 Reactor Technologies, Inc.

Support


Happy building with Reactor! 🚀