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

@bosejs/state

v0.2.0

Published

Fine-grained reactive signals for Bose.

Readme

@bosejs/state

Fine-grained reactive signals for Bosejs.

Install

npm install @bosejs/state

Usage

import { useSignal } from '@bosejs/state';

export default function Counter() {
  const count = useSignal(0);

  const increment = $(() => { count.value++; });

  return `
    <span bose:bind="count">${count.value}</span>
    <button
      bose:on:click="${increment.chunk}"
      bose:state='${JSON.stringify({ count: count.value })}'>
      +
    </button>
  `;
}

API

useSignal(initialValue)

Creates a reactive signal.

const count = useSignal(0);

count.value        // read: 0
count.value = 5   // write: triggers DOM update

bose:bind (HTML attribute)

Bind a DOM node to a signal. The runtime updates the node's text content whenever the signal changes — no re-render, no diffing.

<span bose:bind="count">0</span>

The attribute value must match the variable name used with useSignal.

How signals survive resumption

When the page is SSR-rendered, signal values are serialized into bose:state attributes on interactive elements. When a lazy chunk runs in the browser, the runtime deserializes this state and reconstitutes the signals — so count.value always reflects the current state, not the initial server-rendered value.

SSR Signal Hydration

By default, useSignal(initialValue) always renders with initialValue on the server. Use setSSRContext in a page handler to seed the real server-side value before render:

import { useSignal, setSSRContext } from '@bosejs/state';

export default async function CartPage({ params }) {
  // Seed from server context (cookie, DB, session, etc.)
  const count = await cartStore.getCount();
  setSSRContext({ 'cart-count': count });

  // Resolves to real count on the server, falls back to 0 in the browser
  const cartCount = useSignal(0, 'cart-count');

  return `<span bose:bind="cart-count">${cartCount.value}</span>`;
}

setSSRContext is a no-op in the browser. The Bose Vite plugin automatically isolates each SSR request using AsyncLocalStorage, so concurrent requests never share signal context.

License

MIT © Bosejs Contributors