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

v0.2.19

Published

Ream — Rust-powered Node.js application framework

Readme

@c9up/ream

Rust-powered Node.js application framework. Convention over configuration with native performance.

@c9up/ream ships as a single package containing both the TypeScript framework and prebuilt Rust (NAPI) binaries — consumers never compile anything.

Features

  • IoC Container@Service(), @Inject(), auto-resolution, scopes
  • Lifecycle — register → boot → start → ready → shutdown
  • Router — fluent chaining, groups, params, guards, versioning, named routes + urlFor() URL builder (namedManifest() exposes them to the client)
  • Middleware pipeline — onion pattern, global + named, guard enforcement
  • HTTP server — Rust Hyper via NAPI
  • Static filespublic/ served with ETag, Last-Modified and byte ranges, guarded against escaping the directory (@c9up/ream/storage/provider)
  • Event bus — in-process emitter with optional Redis store (@c9up/ream/events)
  • Scheduler — cron/interval tasks via the @Schedule() decorator (Rust-backed)
  • GraphQL & RPC — built-in GraphQL engine and typed RPC router
  • Security primitives — signed cookies, HMAC, signed URLs, trusted-proxy config (request-filter security — XSS / CSRF / rate-limiting — lives in @c9up/blackhole)
  • Error DX — structured errors, fuzzy matching, pipeline stage context
  • Health check — Kubernetes-compatible /health endpoint
  • Graceful shutdown — SIGTERM/SIGINT with drain timeout

Quick Start

import { Ignitor } from '@c9up/ream'

const app = new Ignitor({ port: 3000 })
  .httpServer()
  .routes((router) => {
    router.get('/hello/:name', async ({ params, response }) => {
      response.status(200).send(`Hello, ${params.name}!`)
    })
  })

await app.start()

Testing

Declare your suites in reamrc.ts, the way AdonisJS declares them in adonisrc.ts, and ream test runs them:

// reamrc.ts
export default defineConfig({
  tests: {
    timeout: 2_000,
    forceExit: false,
    suites: [
      { name: 'unit', files: ['tests/unit/**/*.spec.(js|ts)'] },
      {
        name: 'functional',
        files: ['tests/functional/**/*.spec.ts'],
        timeout: 30_000,
        // The per-suite `configure`. Costs an import of this file in every
        // worker — `configureSuite` in tests/bootstrap.ts does the same for free.
        configure: (suite) => suite.setup(() => startHttpServer()),
      },
    ],
  },
})
ream test                    # every suite, in order
ream test functional         # one suite
ream test --bail --threads=4

ream test sets NODE_ENV=test and loads the .env files itself, before spawning anything: .env.test wins over .env, .env.local is skipped so a developer's local overrides never decide what CI runs, and the shell keeps the last word. The app writes no hook for this — the workers inherit the environment of the process that spawned them.

forceExit: true makes the run call process.exit() once it ends instead of waiting for the event loop to drain — the answer to a pool or a server the app left open. Without it the process exits on its own, so a leaked handle surfaces as a diagnosable hang rather than being swallowed.

The stratification is AdonisJS's: ream reads its rc file and hands the suites to the runner (@c9up/helix), exactly as @adonisjs/core reads adonisrc.ts and hands them to its own runner. helix knows nothing about ream, and ream owns no test execution. tests/bootstrap.ts — plugins, runnerHooks, configureSuite — is helix's, unchanged.

Driving it yourself (a bin/test.ts, a console command) is the same call:

import { runTestsFromRcFile } from '@c9up/helix-plugin-ream/runner'

process.exitCode = await runTestsFromRcFile('./reamrc.ts', {
  suites: process.argv.slice(2),
})

Ecosystem

Every package is standalone and publishable on its own; they consume the Ream universe through the container, never via a static import.

| Package | Description | |---------|-------------| | @c9up/archive | File storage (Local + S3-compatible) | | @c9up/atlas | Data Mapper ORM | | @c9up/atom | Exact decimal arithmetic | | @c9up/aurora | Reactive UI runtime (SSR + hydration) | | @c9up/bay | Job queue (memory + Redis drivers) | | @c9up/blackhole | Security filter — XSS, CSRF, rate-limiting (Rust-native) | | @c9up/chronos | Date/time & recurrence engine | | @c9up/comet | JSON-RPC 2.0 protocol + isomorphic client | | @c9up/echo | Cache (memory + Redis drivers) | | @c9up/eclipse | Distributed locks (owner-checked leases, memory + Redis stores) | | @c9up/eon | Time-series data layer (TDengine-backed) | | @c9up/helix | Framework-agnostic test runtime | | @c9up/helix-plugin-ream | The ream↔helix bridge (boots a Ream app under test) | | @c9up/inker | Server-side templating | | @c9up/nebula | shadcn/ui ported to Aurora, as atomic design | | @c9up/nova | Web Push notifications (VAPID) | | @c9up/parsec | Metrics & telemetry (Prometheus exporter, optional OpenTelemetry) | | @c9up/photon | Frontend rendering engine | | @c9up/prism | Image processing — resize, convert, crop, composite, watermark (Rust-native) | | @c9up/quasar | Redis connections (named, pub/sub, health checks) | | @c9up/ream-cli | CLI & code generators (Rust binary, ream command) | | @c9up/ream-mcp | MCP server — agent-ready framework assistant | | @c9up/relay | Realtime transport (SSE; WebSocket Hub protocol implemented, no server upgrade point yet) | | @c9up/rosetta | Internationalization (i18n) | | @c9up/rover | Mail (SMTP, SES, Mailgun, SendGrid, Brevo, Resend, SparkPost, log) | | @c9up/rune | Validation engine | | @c9up/sigil | Password hashing (argon2, bcrypt, scrypt) | | @c9up/spectrum | Structured logging | | @c9up/station | Admin scaffolding | | @c9up/transit | Federated sign-in (SAML 2.0, LDAP, OpenID Connect, OAuth1, OAuth2) | | @c9up/vellum | PDF (render, read, reshape, stamp, forms, signing, verification) | | @c9up/warden | Authentication |

License

MIT