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

v0.2.0

Published

Reactive core for Gomani — a thin, stable wrapper over a proven fine-grained signals engine.

Readme

@gomani/signals

The reactive core of Gomani — fine-grained signals, wrapped behind a small stable API so the engine underneath stays swappable.

Gomani doesn't reinvent reactivity: signals are the converged, settled answer. This package is a deliberately thin wrapper over @preact/signals-core, exposing Gomani's own surface so the rest of the framework — and, later, the .goma compiler — depends only on this. Everything is isomorphic: the same primitives snapshot initial values during SSR and drive fine-grained DOM updates on the client.

Install

npm install @gomani/signals

API

import { signal, computed, effect, batch, untracked, isSignal } from '@gomani/signals';

const count = signal(0);
const doubled = computed(() => count.value * 2);

const stop = effect(() => {
  console.log(count.value, doubled.value); // runs now, and on every change
  return () => {}; // optional cleanup, runs before each re-run and on stop()
});

batch(() => {
  count.value = 1;
  count.value = 2; // dependents re-run once, after the batch
});

count.peek(); // read without subscribing
untracked(() => count.value); // read without subscribing the surrounding effect
stop(); // tear down the effect

isSignal(count); // true

| Export | Purpose | | --------------- | ------------------------------------------------------------------ | | signal(v) | A writable reactive value (.value, .peek()) | | computed(fn) | A cached, read-only derived value | | effect(fn) | Run now + on change; returns a disposer; fn may return a cleanup | | batch(fn) | Coalesce writes so dependents run once | | untracked(fn) | Read without subscribing | | isSignal(x) | Narrow an unknown to a signal |

License

MIT © Venancio Gomani / Kwacha Kulture.