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

@mark1russell7/render-node

v0.3.0

Published

The reactive node store of render: seats, slots, ordered flow epochs and the NodeOps extension points.

Downloads

2,104

Readme

@mark1russell7/render-node

npm CI license: MIT

The reactive store of render. Each value is a node with an expression, a coeval document. One write starts one epoch. The store evaluates each reader of the node in topological order, and it stops at each value that does not change.

npm i @mark1russell7/render-node @mark1russell7/render-dsl @mark1russell7/render-splay
import { app, lit, ref } from "@mark1russell7/render-dsl";
import { addNode, batch, nodeStore, readValue, setValue } from "@mark1russell7/render-node";
import { standardOps } from "@mark1russell7/render-splay";

const store = nodeStore({ ops: standardOps });
addNode(store, lit(2), "w");
addNode(store, lit(4), "h");
addNode(store, app("*", ref("w"), ref("h")), "area");

setValue(store, "w", 3);
readValue(store, "area"); // { tag: "some", value: 12 }
store.epochStats; // the nodes that the write evaluated and changed

// A batch makes many writes one epoch
batch(store, () => {
  setValue(store, "w", 5);
  setValue(store, "h", 5);
});

A node can be a container of named slots, and a reference reads through the slots. The NodeOps of a store (splash, flow, deref and targets) are its extension points.

The kernel of coeval compiles the expression of a node one time, at each write. Each epoch evaluates the plan. The store is the host thing of the root world. The kernel gives it each path in one call, and the deref op of the store answers. The reads of a node are its free world references (refsOf of the kernel, readsOf). A store value is data, thus a value with the shape of a reference stays a value.

More

Each package of render is ESM, has TypeScript declarations, and works in Node.js 22.12 or later and in browsers. The license is MIT.