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

kloen

v0.17.0

Published

A small, independent signals implementation

Readme

Kloen

Klön, der | kløːn | (North German) leisurely, informal conversation or chat.

Usage / Quick Start

Kloen is a practical signals library

import { signal, computed, effect } from "https://esm.sh/kloen"

const counter = signal(0) 
const double = computed(v => counter() * 2)
effect(() => console.log("Counter:", counter()))

// Update counter an trigger effects
counter(4) 

It uses alien-signals's reactivity system under the hood and its surface API is mostly the same. Some differences exist in order to be able to provide some utility functions that are not possible with alien-signals' default API.

import { signal, computed, effect, update } from "https://esm.sh/kloen"

// update signals using pure transform functions using the `update` utility
const add10 = v => v + 10
update(counter, add10)

counter() // 14
double() // 28

// kloen's effect returns an unsubscribe for cleanups
const unsub = effect(() => console.log(`counter value:`, counter()))

const someSet = signal(new Set())
const size = computed(() => someSet.size)

size() // 0

// Use `mutate` to make changes to the contained value. Useful if you need to store an expensive object
mutate(someSet, s => s.add('item'))

size() // 1

Named Signals

Signals can be named and receive a default value if not yet existing, making it easy to share signals between places where passing it down is not easily possible.

const a = signal.for('counter-a', 0)
a === signal.for('counter-a') // true

Initializer

Named signals can take a function that is only run when the reference did not yet exist.

const repo = signal.for('db', () => new PGlite({ /* ... */ }))

Why?

This is mostly to study signals and understand their various implementations better as well as an exercise in API design.

read more