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

@sheldom/state

v0.1.1

Published

State system package of the sheldom library.

Readme

@sheldom/state

Reactive state for Web Components, without the framework.

@sheldom/state gives you a @state decorator that turns a class field into a reactive one — set it, and requestUpdate() gets called for you. No store, no proxies over your whole object graph, no framework runtime: just a small State<T> primitive and a few decorators built on top of it.

✨ Features

⚡ @state fields

Decorate a field, get automatic re-renders on every change — deduped with Object.is, so setting the same value twice is a no-op.

🌍 Shared state across components

@globalState and useGlobalState let unrelated components read and write the exact same piece of state by name.

👀 @watch a state's changes

React to a state changing without owning it — call a method whenever a named state updates.

🧠 Just a State<T> underneath

Every decorator is a thin layer over a plain State<T> class with subscribe/unsubscribe. Use it directly if you don't need the decorators.

🔌 Framework-agnostic

Works with anything that implements a tiny Updatable contract — @sheldom/core's Component, or your own classes.

📦 Install

npm install @sheldom/state

🚀 Usage

import { Component } from "@sheldom/core";
import { html } from "@sheldom/dom";
import { state, watch } from "@sheldom/state";

export default class Counter extends Component {
    @state count = 0;

    @watch("count")
    onCountChanged(value: number) {
        console.log("count is now", value);
    }

    render() {
        return html`
            <button @click=${() => this.count++}>Count: ${this.count}</button>
        `;
    }
}

Share a value across components with @globalState:

import { Component } from "@sheldom/core";
import { globalState } from "@sheldom/state";

export default class Cart extends Component {
    @globalState("cart-count") itemCount = 0;
}

Any other component using @globalState("cart-count") reads and writes the same value — updating one re-renders every component watching it.

Prefer no decorators at all? Use State<T> directly:

import { State } from "@sheldom/state";

const theme = new State<"light" | "dark">("light");
const unsubscribe = theme.subscribe((value) => console.log("theme:", value));

theme.value = "dark"; // logs "theme: dark"

🌱 Part of the Sheldom toolkit

@sheldom/state only depends on @sheldom/core-contracts — it doesn't need @sheldom/core or any rendering engine to work. Most projects should install sheldom instead, which bundles it together with Component and html.

📄 License

MIT — see LICENSE.