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

@katabatic/signals

v1.0.6

Published

A lightweight, proxy-based reactive signal library for JavaScript.

Readme

@katabatic/signals

A lightweight, proxy-based reactive signal library for JavaScript.

  • Proxy-Based Reactivity - Transparent tracking via JavaScript Proxies
  • Event-Driven - Built on EventTarget API
  • Microtask Scheduling - Optimized effect batching

Installation

npm install @katabatic/signals

Quick Start

import { signal, effect } from '@katabatic/signals'

// Create signal
const count = signal({ value: 0 })

// Create effect
effect(() => {
  console.log(`Count: ${count.value}`)
})

count.value = 5 // Triggers effect

API

signal(object)

Creates a reactive signal from an object or array.

const obj = signal({ x: 1, y: 2 })
const arr = signal([1, 2, 3])

Objects and Arrays are wrapped in a proxy while all other data types are left untouched.

effect(fn)

Creates an effect that re-runs when tracked signal properties change.

const count = signal({ value: 0 })

effect(() => {
  console.log(count.value) // Automatically tracked
})

The effect function can return an optional cleanup function. Effects run asynchronously by default.

compute(fn)

Creates a derived signal that re-computes when dependencies change.

const count = signal({ value: 0 })
const doubled = compute(() => count.value * 2)

effect(() => {
    console.log(doubled()) // Returns current value
})

The effect is triggered only if the computed value changes.

boundary(fn)

Creates an isolation boundary preventing effect tracking propagation.

effect(() => {
    boundary(() => {
        // signals here are not tracked by the outer effect
    })
})

untracked(fn)

Executes code without dependency tracking.

const count = signal({ value: 0 })

effect(() => {
  console.log(untracked(() => count.value)) // Not Tracked
})

Nested Objects & Arrays

Signals handle nested structures automatically:

const state = signal({
  user: { name: 'Alice', tags: ['admin'] }
})

effect(() => {
  console.log(state.user.name)      // Tracked
  console.log(state.user.tags[0])   // Tracked
})

state.user.name = 'Bob'              // Re-runs effect
state.user.tags.push('moderator')   // Re-runs effect

Class based signals

A Signal can also be created by extending the Signal class.

import { Signal } from '@katabatic/signals'

class Count extends Signal {
    static observedProperties = ['value']

    #unit

    constructor() {
        super()
        this.value = 0
    }

    get unit() {
        this.trackEvent('unitChanged')
        return this.#unit
    }

    set unit(unit) {
        this.#unit = unit
        this.dispatchEvent(new SignalEvent('unitChanged'))
    }
}

Dependency tracking can either be declarative with the static observerProperties property or explicit using the dispatchEvent and trackEvent methods.

License

MIT


Part of the Katabatic project.