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/mithril

v0.7.1

Published

Mithril.js adapter for wc-bindable protocol

Readme

@wc-bindable/mithril

Mithril.js adapter for the wc-bindable protocol.

Bridges the protocol's bind() into Mithril's oncreate / onremove lifecycle and Mithril's redraw() cycle, so a Web Component's declared properties show up as plain state you can read inside view().

Install

npm install @wc-bindable/mithril mithril

API

wcBindable(el, onUpdate): unbind

Low-level helper. Call it from any lifecycle hook that gives you the DOM node; the adapter does no redraw — you decide what to do with each update.

| Parameter | Type | Description | |---|---|---| | el | HTMLElement | 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?, options?): WcBindableState<V>

Stateful helper. Holds a values object, mutates it as events arrive, and calls m.redraw() so your view() rerenders automatically.

Returns { values, oncreate, onremove } — wire those directly into your component.

| Option | Type | Default | |---|---|---| | redraw | () => void | () => m.redraw() — override to use m.redraw.sync() or batch redraws |

Usage

oncreate and onremove must run on the bindable element itself — Mithril hands the hook the vnode whose DOM node it is attached to, and the adapter only binds if that node implements the protocol. So always attach the hooks to the <my-input> vnode, not to a wrapping component or <div>:

import m from "mithril";
import { createWcBindable } from "@wc-bindable/mithril";

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

  return {
    view: () =>
      m("div", [
        m("my-input", {
          oncreate: binder.oncreate,
          onremove: binder.onremove,
        }),
        m("output", `value: ${binder.values.value}`),
        m("output", `checked: ${binder.values.checked}`),
      ]),
  };
};

m.mount(document.body, Form);

If your component's view root is the bindable element (no wrapper), you can attach the hooks at the component level instead — vnode.dom will then be the bindable element:

const Input = () => {
  const binder = createWcBindable<{ value: string }>({ value: "" });
  return {
    oncreate: binder.oncreate,
    onremove: binder.onremove,
    view: () => m("my-input"),
  };
};

Low-level usage

import m from "mithril";
import { wcBindable } from "@wc-bindable/mithril";

const Form = () => {
  const state: Record<string, unknown> = { value: "" };
  let unbind: (() => void) | null = null;

  return {
    view: () =>
      m("div", [
        m("my-input", {
          oncreate(vnode) {
            unbind = wcBindable(vnode.dom as HTMLElement, (name, value) => {
              state[name] = value;
              m.redraw();
            });
          },
          onremove() {
            unbind?.();
          },
        }),
        m("output", state.value as string),
      ]),
  };
};

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