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

@gomani/runtime

v0.2.0

Published

Tiny client runtime: mount islands, on-demand hydration.

Downloads

161

Readme

@gomani/runtime

The tiny client runtime of Gomani: a fine-grained reactive DOM renderer and on-demand island hydration.

Loaded once per page — and only when the page actually has islands — this is the single shared cost every island chunk reuses. There is no global startup pass ("resumability-lite"): start() only wires cheap triggers, and an island's chunk is fetched and rendered only when its strategy fires. Interactive cost is decoupled from app size (P3).

start() — boot island hydration

Put this once on any page that has islands. It scans for <gomani-island> markers (emitted by @gomani/core's renderToString) and wires each one's load trigger.

import { start } from '@gomani/runtime';

start(); // reads island name→URL from <script type="application/json" id="gomani-islands">

Each island wakes on its own strategy — load, idle, visible (default), interaction, or media — then its chunk is imported and the component is mounted into the marker, replacing the server HTML with a live, reactive render seeded from the marker's serialized props. Already-hydrated islands are skipped, so start() is safe to call more than once.

start({
  root: document, // where to scan (default document)
  manifest: { counter: '/islands/counter.js' }, // name → chunk URL (else read from the DOM)
  loader: (name) => import(urlFor(name)), // override how a chunk is fetched
});

mount() — reactive DOM rendering

The renderer islands use internally, exported for advanced/manual mounting. No virtual DOM, no diffing: a signal used as a child or attribute is bound to exactly one text node or attribute, so an update touches only that node.

import { mount } from '@gomani/runtime';
import { signal } from '@gomani/signals';

const count = signal(0);
const dispose = mount(
  <button onClick={() => count.value++}>{count}</button>,
  document.getElementById('app')!,
);
// dispose() tears down every effect and event listener.

License

MIT © Venancio Gomani / Kwacha Kulture.