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

@c9up/ream-cli-win32-x64

v0.3.15

Published

Rust-native CLI for the Ream framework. Instant startup, no Node.js boot penalty.

Downloads

1,686

Readme

ream

Rust-native CLI for the Ream framework. Instant startup, no Node.js boot penalty.

Install

npm install -g @c9up/ream-cli

Commands

Run ream --help (or ream <command> --help) for the authoritative, always up-to-date list. What the binary itself defines:

# Scaffolding
ream new my-app                       # create a new Ream project
ream template kitchen-sink            # install a project template from its upstream repo

# Development
ream dev                              # dev server + whatever builds the assets, under one Ctrl-C
ream build                            # assets, then TypeScript into dist/
ream start                            # run production (spawns node)
ream test                             # the suites declared in reamrc.ts
ream repl                             # a Node REPL with the application booted

# Code generation
ream make:controller order Order      # app/order/OrderController.ts
ream make:service order Payment       # app/order/PaymentService.ts
ream make:entity order OrderItem      # app/order/OrderItem.ts
ream make:validator order CreateOrder
ream make:module order Order          # entity + controller + validator + migration
ream make:provider Stripe
ream make:command app:provision       # commands/app-provision.ts, discovered automatically
ream make:middleware auth --stack router
ream make:event orderShipped
ream make:listener sendMail --event orderShipped
ream stubs:publish controller         # copy a make: template into stubs/make/ to edit it

# Packages
ream add @c9up/atlas                  # install a package AND run its configure() hook
ream configure @c9up/photon           # (re-)run a package's configure() hook

# Integrations / tooling
ream mcp install                      # manage the Ream MCP server registration (.mcp.json)
ream generate:key                     # a fresh APP_KEY into .env
ream inspect                          # routes, providers, container bindings
ream list                             # every command — this binary's and the app's

# Diagnostics
ream doctor                           # environment health checks
ream info                             # version info

Every make: command takes --dry-run (print the plan as JSON, write nothing) and --force (overwrite what is there).

Anything else is dispatched to the application's console kernel with its flags intact, so a package's commands and the app's own run the same way:

ream migrate                          # @c9up/ream, across every registered store
ream migration:run                    # @c9up/atlas
ream make:migration create_orders_table
ream schedule:list
ream provision --email [email protected]   # the app's own

Build from source

cargo build --release
# Binary at target/release/ream

Assets

ream dev runs the server and whatever builds your assets as one thing, and ream build builds the assets before TypeScript. Declare them in reamrc.ts:

export default {
  assets: {
    devServer: { command: 'pnpm', args: ['css:watch'] },
    build: { command: 'pnpm', args: ['css'] },
  },
}

Output is line-prefixed per process, and when one stops the other is stopped with it — a Ctrl-C leaves no orphan watcher holding the output file. Without this, an app ends up wiring concurrently -k itself.

Both keys are optional: with no assets, ream dev and ream build behave exactly as before.

License

MIT