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

@pyreon/machine

v0.11.3

Published

Reactive state machines for Pyreon — constrained signals with type-safe transitions

Readme

@pyreon/machine

Reactive state machines for Pyreon. A machine is a constrained signal — it can only hold specific values and transition between them via specific events. Type-safe states and events inferred from the definition.

Install

bun add @pyreon/machine

Quick Start

import { createMachine } from '@pyreon/machine'

const machine = createMachine({
  initial: 'idle',
  states: {
    idle: { on: { FETCH: 'loading' } },
    loading: { on: { SUCCESS: 'done', ERROR: 'error' } },
    done: {},
    error: { on: { RETRY: 'loading' } },
  },
})

machine()              // 'idle' — reads like a signal
machine.send('FETCH')  // transition to 'loading'
machine.matches('loading') // true — reactive in effects/JSX

// Reactive in JSX
{() => machine.matches('loading') && <Spinner />}
{() => machine.matches('done') && <Results />}

Guards

Conditional transitions using guard functions:

const form = createMachine({
  initial: 'editing',
  states: {
    editing: {
      on: { SUBMIT: { target: 'submitting', guard: () => isValid() } },
    },
    submitting: { on: { SUCCESS: 'done', ERROR: 'editing' } },
    done: {},
  },
})

API

createMachine(config)

Create a reactive state machine. Config: initial (starting state) and states (state/event map).

Returns Machine:

| Property | Description | | --- | --- | | machine() | Read current state (reactive) | | send(event, payload?) | Trigger a transition | | matches(...states) | Check if in one of the given states (reactive) | | can(event) | Check if event would trigger a valid transition | | nextEvents() | Available events from current state | | reset() | Return to initial state | | onEnter(state, callback) | Fire callback when entering a state | | onTransition(callback) | Fire on any transition |

Use signals alongside machines for data. The machine manages transitions, signals manage data.

License

MIT