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/aurora

v0.1.32

Published

Aurora — reactive UI runtime for the Ream framework. Tagged-template DOM, signal-based state, isomorphic SSR + hydration, zero build step.

Readme

@c9up/aurora

Reactive UI runtime for the Ream framework — tagged-template DOM, signal-based state, isomorphic SSR + hydration, zero build step.

Part of Ream — a Rust-powered, AdonisJS-compatible Node.js framework. Independent, publishable package.

Installation

pnpm add @c9up/aurora
ream configure @c9up/aurora

Usage

Register the provider in your app, then configure it under config/aurora.ts:

// reamrc.ts
providers: [
  () => import('@c9up/aurora/provider'),
]
// config/aurora.ts
export default {
  pages: {
    root: new URL('../resources/pages', import.meta.url).pathname,
  },
  root: {
    tag: 'main',
    class: 'min-h-screen',
  },
  shared: async (ctx) => ({
    auth: { user: ctx.auth?.user ?? null },
    flash: ctx.session?.flashMessages?.all?.() ?? {},
    errors: ctx.session?.flashMessages?.get?.('errors') ?? {},
  }),
}

Controllers stay thin, like Adonis/Inertia controllers:

export default class DashboardController {
  async show({ aurora }) {
    return aurora.render('dashboard/show', {
      stats: await loadStats(),
    })
  }
}

Dev live-reload (HMR)

Pages are dynamic-imported per request; aurora dev-busts the page module by mtime, but a page's transitive imports (components/layouts/services) stay cached until you restart. Enable graph-aware SSR HMR — the AdonisJS way — with hot-hook:

pnpm add -D hot-hook @hot-hook/runner
// package.json
{
  "scripts": {
    "dev": "hot-runner --node-args=--import=tsx --node-args=--import=hot-hook/register bin/server.ts"
  },
  "hotHook": { "boundaries": ["./resources/pages/*.js"] }
}

Editing a page or any component it imports now hot-reloads the SSR with no restart. Point boundaries at page entries only (./resources/pages/*.js, not **/*.js) — hot-hook requires boundary files to be dynamically imported, so a statically-imported component matched by the glob forces a full reload. aurora itself needs no change.

Entry points

  • @c9up/aurora — main API: reactive primitives (signal/effect/html/component/hydrate) plus the client toolkit — WebStorage/persistedSignal, reactive browser signals (prefersDark/online/windowSize/…), SPA navigation (navigate/queryParam), cookie/clipboard/share, the HttpClient fetch wrapper, createRpcClient() (JSON-RPC 2.0), command() (async action + reactive loading/data/error), form() (reactive form controller; optional rune validation + rosetta i18n), urlFor() (isomorphic named-route URLs, paired with Ream's router.namedManifest()), and cn() (zero-dependency Tailwind v4 class merge — clsx + tailwind-merge reimplemented)
  • @c9up/aurora/provider — Ream IoC provider
  • @c9up/aurora/services/main — container service accessor
  • @c9up/aurora/relay — realtime adapter
  • @c9up/aurora/ssr — server-side rendering
  • @c9up/aurora/hydrate — client hydration
  • @c9up/aurora/server — server-only helpers and types (AuroraManager, Pages, renderPage, serveAssets, SharedProps, SharedPropsResolver)

Adonis / Inertia parity

Implemented in Aurora:

  • provider + IoC service;
  • ctx.aurora.render(name, props, options);
  • named page rendering from routes/controllers;
  • shared props per request via shared;
  • root tag/class customization;
  • named-route manifest for urlFor();
  • asset/version marker in page data;
  • SSR + hydration payload.

Still intentionally tracked as remaining work:

  • @adonisjs/vite-equivalent frontend integration: asset bundling, dev manifest and browser-asset HMR (SSR page-module HMR is available today via hot-hook — see Dev live-reload);
  • full Inertia navigation semantics: preserve state, history encryption, version mismatch handling and client-side visit lifecycle;
  • generated page-name types.

Security notes

  • renderPage() isolates SSR cookies and route manifests per request. Pages can read cookieState() and urlFor() across async boundaries without leaking another concurrent request's state.
  • renderPage() and AuroraManager.render() support Adonis/Inertia-style shared props via shared, plus root element customization via rootTag, rootClass or config.aurora.root.
  • HttpClient does not send managed bearer/default Authorization headers to cross-origin absolute URLs by default. Set allowCrossOriginAuth: true only when the external origin is intentional and trusted, or pass an explicit per-request Authorization header.
  • wireLiveEvents() accepts an authorize(ctx, body) hook. Use it to bind live event POSTs to the same auth/CSRF/owner policy as the page that mounted the live session.
  • redirect(), replace() and navigate() reject javascript:, vbscript: and data: URLs.
  • auroraRoute() is the legacy low-level route helper. Prefer the provider / ctx.aurora.render() pipeline for Adonis-style applications.

License

MIT