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

@cyrene/core

v1.0.0-beta.2

Published

The next generation core runtime for Cyrene Framework.

Readme

@cyrene/core

The runtime for Cyrene — signals, the DOM renderer, stores, the scheduler, SSR, and the router primitives. This is the package you install first; most apps only ever import from here.

No virtual DOM. State is signal-based and updates are fine-grained: when a signal changes, only the exact text nodes and attributes that read it are touched, not a re-rendered tree.

npm install @cyrene/core@beta

Currently published under the beta tag while the 1.0 API settles — the @beta tag is required. A plain npm install @cyrene/core resolves latest, which still points at a stale, broken beta.0 build until it is retagged at GA.

A quick component

You can write Cyrene entirely in .tsx — no .cyr toolchain required. h is the JSX factory (configure jsxFactory: "h"), and a component returns a render thunk:

import { h, createSignal, render } from "@cyrene/core";

function Counter() {
  const [count, setCount] = createSignal(0);
  return () => (
    <button onclick={() => setCount(c => c + 1)}>
      count is {count()}
    </button>
  );
}

render(() => <Counter />, document.getElementById("app")!);

createSignal returns a [read, write] pair; calling count() inside a view subscribes that spot to the signal. createMemo derives values lazily, createEffect runs side effects, createStore / defineStore handle larger state. Control flow is <For>, <Show>, <Switch>, <Suspense>, <ErrorBoundary>.

Entry points

The barrel is intentionally split so browser bundles stay small — import from the subpath you need rather than the root in server/dev code:

| Import | For | |---|---| | @cyrene/core | client runtime (signals, render, h, control flow) | | @cyrene/core/ssr | renderToString / streaming — server only, no DOM | | @cyrene/core/server | SSR + middleware (Node/Bun) | | @cyrene/core/labs | experimental primitives (API may change in 1.x) | | @cyrene/core/jsx-runtime | automatic JSX runtime (no manual h import) | | @cyrene/core/devtools | DevTools bridge | | @cyrene/core/testing | test helpers |

Version

@cyrene/core exports version, buildNumber, and fullVersion if you want to display or log which build you're on.

Docs and guides: https://www.cyrenejs.com · MIT licensed.