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

cami

v0.4.2

Published

A minimalist & flexible toolkit for interactive islands & state management in hypermedia-driven web applications.

Readme

Cami.js

Cami.js is a drop-in toolkit for adding interactive islands to server-rendered or static HTML. Its CDN bundle fits multi-page applications without a build step. Compiled applications can use the same API through an ES module with strong TypeScript declarations.

Version 0.4: APIs may change before 1.0.

Start with a script tag

<cami-counter></cami-counter>
<script src="https://unpkg.com/[email protected]/build/cami.cdn.js"></script>
<script src="./counter.js"></script>
const { html, ReactiveElement } = cami

class CamiCounter extends ReactiveElement {
  count = 0

  template() {
    return html`
      <button @click=${() => this.count--}>−</button>
      <output>${this.count}</output>
      <button @click=${() => this.count++}>+</button>
    `
  }
}

customElements.define('cami-counter', CamiCounter)
import { html, ReactiveElement, store } from 'cami'

interface CounterState {
  count: number
}

const counter = store<CounterState>({
  name: 'counter',
  state: { count: 0 },
})

counter.defineAction('increment', ({ state }) => {
  state.count++ // state is a typed Draft<CounterState>
})

counter.defineAction('decrement', ({ state }) => {
  state.count--
})

class CamiCounter extends ReactiveElement {
  template() {
    return html`
      <button @click=${() => counter.dispatch('decrement')}>−</button>
      <output>${counter.state.count}</output>
      <button @click=${() => counter.dispatch('increment')}>+</button>
    `
  }
}

customElements.define('cami-counter', CamiCounter)

State and actions are checked against CounterState. Misspell a field and tsc tells you at build time.

Use JavaScript or TypeScript in a compiled project

npm install cami

The browser-global CDN bundle is the shortest path for an MPA or server-rendered page. The ES module works in JavaScript and TypeScript builds and ships with type declarations.

Current public surface

  • Components and templates: ReactiveElement, html, svg, repeat, keyed, unsafeHTML, useImage
  • Shared state: store, ObservableStore, actions, memos, queries, mutations, hooks, state machines
  • Browser integration: URLStore and versioned localStorage

Observable, ObservableState, and effect() remain available only for Cami 0.3 compatibility. New code should use component fields, stores, and afterRender().

Read the documentation, start with the first-island tutorial, or use the API reference.

Development

Install dependencies:

npm install

Run the main checks:

npm run type-check
npm test
npm run build
npm run build:docs

Serve the documentation locally:

npm run docs:serve

Then open http://127.0.0.1:8000/.

Project status

Cami is pre-1.0. Pin the version in production and review release changes before upgrading.

License

MIT © Kenn Costales