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

@hoosk/minisignals

v1.1.0

Published

Minimal agnostic signals library

Readme

@hoosk/minisignals

The framework-agnostic core of the minisignals library.

This package provides the fundamental reactive primitives: signal, effect, computed, batch, and untracked. It has zero dependencies and is built for maximum performance and a minimal footprint.

Installation

npm install @hoosk/minisignals

Basic Usage

import { signal, effect, computed, batch, untracked } from '@hoosk/minisignals';

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

effect(() => {
  console.log(`Count: ${count.value}, Double: ${double.value}`);
});

count.value = 1; // Logs: Count: 1, Double: 2

// Batch multiple writes into a single notification pass
batch(() => {
  count.value = 10;
  count.value = 20;
}); // Logs once: Count: 20, Double: 40

Performance

The core is built on a linked-list dependency graph with O(1) dependency lookup (currentLink pointer), lazy computed evaluation (dirty flag, no eager recomputation), and class-based signal instances for V8 monomorphization.

Benchmark results on Node.js (warmup 150 ms, sample 350 ms):

── Signal ────────────────────────────────────────────────────
scenario                               ops/s        time/op
─────────────────────────────────────────────────────────────
signal-read                    420.38M ops/s      2.38 ns/op
signal-write-no-subscribers    210.86M ops/s      4.74 ns/op
signal-write-same-value        760.84M ops/s      1.31 ns/op

── Effect ────────────────────────────────────────────────────
scenario                               ops/s        time/op
─────────────────────────────────────────────────────────────
effect-fanout-write             17.77K ops/s     56.27 µs/op
effect-create-dispose            5.86M ops/s    170.66 ns/op
effect-dynamic-deps              7.08M ops/s    141.15 ns/op

── Computed ──────────────────────────────────────────────────
scenario                               ops/s        time/op
─────────────────────────────────────────────────────────────
computed-chain                  51.07K ops/s     19.58 µs/op
computed-cached-read            44.59M ops/s     22.42 ns/op
computed-batched-writes-no-read 742.71K ops/s     1.35 µs/op
computed-batched-writes-then-read 706.54K ops/s   1.42 µs/op

Run npm run bench to reproduce locally.

For full documentation and advanced features, please refer to the main repository README.