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

@tahaghafuri/tinyfsm

v1.1.0

Published

A tiny (~600B) zero-dependency finite state machine for JavaScript & TypeScript

Readme

@tahaghafuri/tinyfsm

A tiny (~700B) zero-dependency finite state machine for JavaScript & TypeScript.

npm size license

No boilerplate. No classes. No runtime overhead. Just states and events.

import { createMachine } from '@tahaghafuri/tinyfsm';

const fetcher = createMachine({
  initial: 'idle',
  states: {
    idle:    { on: { FETCH:   'loading' } },
    loading: { on: { RESOLVE: 'success', REJECT: 'error' } },
    success: { on: { RESET:   'idle' } },
    error:   { on: { RETRY:   'loading', RESET: 'idle' } },
  },
});

fetcher.send('FETCH');     // → loading
fetcher.send('RESOLVE');   // → success
fetcher.is('success');     // true

Install

npm install @tahaghafuri/tinyfsm

CDN:

<script src="https://cdn.jsdelivr.net/npm/@tahaghafuri/tinyfsm/dist/tinyfsm.umd.min.js"></script>

API

| Method | Returns | Description | |--------|---------|-------------| | .state | S | Current state (readonly) | | .send(event) | boolean | Send event, returns true if transition occurred | | .on(listener) | () => void | Subscribe to changes, returns unsubscribe fn | | .can(event) | boolean | Check if event triggers transition from current state | | .is(state) | boolean | Check if current state matches |

TypeScript

Fully typed with generics — invalid states and events are caught at compile time.

type State = 'idle' | 'loading' | 'success' | 'error';
type Event = 'FETCH' | 'RESOLVE' | 'REJECT' | 'RESET';

const machine = createMachine<State, Event>({ ... });

Lifecycle hooks

const door = createMachine({
  initial: 'closed',
  states: {
    closed: {
      on: { OPEN: 'open' },
      onExit: (to) => console.log(`leaving closed → ${to}`),
    },
    open: {
      on: { CLOSE: 'closed' },
      onEnter: (from) => console.log(`entered open from ${from}`),
    },
  },
});

Why not XState?

XState is excellent for complex machines. @tahaghafuri/tinyfsm is for the other 90% — loading states, UI toggles, wizard steps — where you just need something that works in under 1KB.

License

MIT