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

@kayahr/signal

v5.2.0

Published

Standalone signals library for browser and Node.js

Readme

signal

GitHub | NPM | API Doc

Small, framework-independent signals for TypeScript.

signal provides a small reactive core with explicit ownership, lazy memos, synchronous effects and async resources. Its API is heavily inspired by SolidJS while staying usable as a standalone library in browsers and Node.js, without framework lifecycles.

Observable interop is available through @kayahr/observable.

Scope management and ownership boundaries are provided by @kayahr/scope.

Features

  • Writable signals with configurable equality
  • Lazy memos with dynamic dependency tracking
  • Synchronous effects with cleanup and previous-value support
  • Optional ownership scopes
  • Synchronous batching and explicit untrack
  • Async resources with loading, error, reload and disposal control
  • Array signals without deep array comparisons
  • Observable interop through toSignal, toObservable and toSubscriber

Installation

npm install @kayahr/signal

Examples

Use signals directly when no explicit ownership boundary is needed:

import { createEffect, createMemo, createSignal } from "@kayahr/signal";

const [ count, setCount ] = createSignal(0);
const doubled = createMemo(() => count() * 2);

createEffect(() => {
    console.log(`count=${count()} doubled=${doubled()}`);
});

setCount(1);
setCount(previous => previous + 1);

Use a scope when you want explicit ownership and later cleanup for a whole reactive subgraph:

import { createScope } from "@kayahr/scope";
import { ResourceStatus, createEffect, createMemo, createResource, createSignal } from "@kayahr/signal";

const scope = createScope();
const { setCount, setUserId } = scope.run(() => {
    const [ count, setCount ] = createSignal(0);
    const doubled = createMemo(() => count() * 2);
    const [ userId, setUserId ] = createSignal(1);
    const [ user, resource ] = createResource(userId, async (id, abortSignal) => {
        const response = await fetch(`/api/users/${id}`, { signal: abortSignal });
        return response.json() as Promise<{ name: string }>;
    });

    createEffect(() => {
        console.log(`count=${count()} doubled=${doubled()}`);
        if (resource.status() === ResourceStatus.Ready) {
            console.log(user()?.name);
        }
    });

    return { setCount, setUserId };
});

setCount(1);
setCount(previous => previous + 1);
setUserId(2);

// ...
scope.dispose();

Documentation