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

@frondruntime/core

v0.0.3

Published

Effect-powered Frond runtime core with MobX-facing node state.

Readme

@frondruntime/core

Core Frond runtime package: node authoring, graph execution, lifecycle, diagnostics, signals, and test harnesses.

Install

bun add @frondruntime/core effect mobx

effect is a peer dependency for Effect-facing driver and runtime APIs. mobx is a peer dependency because Frond node state is MobX-backed and must share the app's MobX runtime.

What It Owns

  • createRuntime and the runtime client.
  • NodeBase, NodeSpec, node spec constructors, tags, keys, dependencies, and result commits.
  • Driver.Async and Driver.Effect authoring wrappers.
  • Graph/runtime types under Frond.Graph, Frond.Runtime, Frond.Events, Frond.Signals, and Frond.Diagnostics.
  • MobX-facing node helpers under Frond.MobX.
  • Testing helpers under @frondruntime/core/testing.

Minimal Node

import * as Frond from "@frondruntime/core";

type SessionSpec = Frond.NodeSpec<{
  readonly args: Frond.Args.None;
  readonly key: Frond.Key.Singleton;
  readonly result: { readonly userId: string | null };
}>;

export class SessionNode extends Frond.NodeBase<SessionSpec> {
  static readonly spec = Frond.serviceSpec<SessionSpec>({
    tag: Frond.tag("app/session"),
    key: () => Frond.Key.singleton(),
    driver: Frond.Driver.Async<SessionSpec>({
      acquire: Frond.Driver.Acquire(async () => ({ userId: null })),
    }),
  });

  get isSignedIn(): boolean {
    return this.result.userId !== null;
  }
}

Runtime Usage

const runtime = Frond.createRuntime();
const session = runtime.client.node(SessionNode, Frond.Args.none);

await session.ensureReady();
const read = session.read();

Only ready reads expose the authored node instance. Pending, error, invalid, unavailable, and unwired reads expose lifecycle data, not partial node objects.

Testing

import * as FrondTest from "@frondruntime/core/testing";

The testing subpath includes runtime harnesses, deferred drivers, and spec helpers used to test node behavior without React.

Docs

  • Install: https://frondruntime.dev/docs/start/install
  • First node: https://frondruntime.dev/docs/start/first-node
  • Public surface: https://frondruntime.dev/docs/reference/public-surface

Release notes for this package are generated from Conventional Commits. Squash-merged PR titles provide the release-note subject for this package. Release smoke tests verify GitHub release metadata before npm publishing.