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

@wc-bindable/signals

v0.7.1

Published

TC39 Signals (signal-polyfill) adapter for wc-bindable protocol

Readme

@wc-bindable/signals

TC39 Signals proposal adapter for the wc-bindable protocol, built on signal-polyfill.

Bridges the protocol's bind() into Signal.State, so each declared property of a Web Component is exposed as a reactive signal you can read from any Signal.Computed or Signal.subtle.Watcher — including frameworks and libraries that already consume the polyfill.

The Signals proposal is at Stage 1. The polyfill API and this adapter will likely change as the proposal advances.

Install

npm install @wc-bindable/signals signal-polyfill

API

wcBindable(el, onUpdate): unbind

Low-level helper. Call it with the DOM node and a callback that receives every property update. The adapter does no reactivity wiring — you decide what to do with each update (typically writing to a Signal.State you control).

| Parameter | Type | Description | |---|---|---| | el | Element | The Web Component DOM node | | onUpdate | (name: string, value: unknown) => void | Called once per declared property on initial sync, and again on every change event |

Returns an unbind function. If el does not implement the wc-bindable protocol, the helper is a no-op and the returned function is safe to call.

createWcBindable<V>(initialValues?): WcBindableBinder<V>

Stateful helper. Pre-creates one Signal.State per key in initialValues and keeps each signal's value in sync with the component's matching declared property.

Returns { signals, bind, unbind }. Call bind(el) to attach to the element (safe to call before or after it is connected to the DOM — the initial-value read is deferred via syncOn: "connect"); call unbind() when you're tearing the view down. Read the current value with signals.<name>.get(); observe changes by wrapping that read in a Signal.Computed and attaching a Signal.subtle.Watcher.

import { Signal } from "signal-polyfill";
import { createWcBindable } from "@wc-bindable/signals";

const binder = createWcBindable<{ value: string; checked: boolean }>({
  value: "",
  checked: false,
});

const el = document.querySelector("my-input")!;
binder.bind(el);

const derived = new Signal.Computed(
  () => `value=${binder.signals.value.get()} checked=${binder.signals.checked.get()}`,
);

const watcher = new Signal.subtle.Watcher(() => {
  queueMicrotask(() => {
    for (const s of watcher.getPending()) s.get();
    console.log(derived.get());
    watcher.watch();
  });
});

watcher.watch(derived);
derived.get(); // prime

Properties emitted by the component that are not in initialValues are created lazily on first event, accessible via binder.signals[name].

Usage

import { Signal } from "signal-polyfill";
import { createWcBindable } from "@wc-bindable/signals";
import "./my-counter.js";

const binder = createWcBindable<{ count: number }>({ count: 0 });

const el = document.createElement("my-counter");
binder.bind(el); // initial-sync is deferred until the element is connected
document.body.appendChild(el);

const out = document.createElement("p");
document.body.appendChild(out);

const view = new Signal.Computed(() => `count: ${binder.signals.count.get()}`);

const watcher = new Signal.subtle.Watcher(() => {
  queueMicrotask(() => {
    for (const s of watcher.getPending()) s.get();
    out.textContent = view.get();
    watcher.watch();
  });
});

watcher.watch(view);
out.textContent = view.get(); // initial render

Low-level usage

When you want to manage your own Signal.State objects (e.g. to merge multiple bindable elements into one piece of state), use the low-level helper:

import { Signal } from "signal-polyfill";
import { wcBindable } from "@wc-bindable/signals";

const value = new Signal.State("");

const el = document.createElement("my-input");
document.body.appendChild(el);
const unbind = wcBindable(el, (name, v) => {
  if (name === "value") value.set(v as string);
});

// later
unbind();

Specification

The protocol contract this adapter implements lives in SPEC.md; the optional input/command invocation surface and the remote wire format live in SPEC-extensions.md. Runnable conformance vectors are in CONFORMANCE.md.

License

MIT