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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@tylerb/mek

v0.0.13

Published

A user-friendly finite state machine library for TypeScript

Downloads

13

Readme

Mek

A DX/performance focused finite state machine package for TypeScript.

This package allows you to create readable and performant state machines. The UML state machine spec is not followed. I've just created something I find useful for writing predictable/readable logic flows that loosely follows the concept of state machines. I don't care much about it being correct, only about it being useful and fast!

This library allows for extremely performant synchronous operations without blocking the event loop. Check the benchmark by running pnpm run bench. You'll see that using this library to write 20k files synchronously is much faster than doing the same in a while loop (sync or async!) and is slightly faster than doing it in a recursive function.

The benchmark is admittedly naive, but this is a personal project and I don't have the time to improve it too much. Perhaps one day I will make some proper benchmarks :)

Usage

Check the examples/tests to see what it can do.

  1. Install pnpm install @tylerb/mek

  2. Create a machine

import { create } from "@tylerb/mek"

const ExampleMachine = create.machine(() => ({
  name: "ExampleMachine",
  // states: ...
}))
  1. Create some states w/ lifecycles and add them to the machine
import { create, cycle } from "@tylerb/mek"

const ExampleMachine = create.machine(() => ({
  name: "ExampleMachine",

  states: {
    StateTwo,
    StateOne,
  },

  initialState: StateOne, // if this is omitted it will use object key order in the states object
}))

const StateOne = create.state(() => ({
  machine: ExampleMachine, // each state and machine reference each other so you can jump around your machine and states quickly with go-to-definition in your IDE!

  life: [
    cycle({
      name: "Give the state lifecycle a name (helps with debugging)",
      run: () => {
        console.log(`Each life cycle fn will run in order`)
      },
    }),

    cycle({
      name: "Ok moving over to state two",
      if: () => ExampleMachine.transitionCount < 10, // if you include an "if" function, the cycle will only run/thenGoTo if this returns true
      run: () => {
        // returning an object from any cycle will make it available in the next one on the "context" function argument
        return {
          hello: "there",
        }
      },
      thenGoTo: StateTwo,
    }),

    cycle({
      name: "Exit!",
      run: () => {
        ExampleMachine.stop()
      },
    }),
  ],
}))

const StateTwo = create.state(() => ({
  machine: ExampleMachine,

  life: [
    cycle({
      name: "Example two",
      if: ({ context }) => Boolean(context.hello),
      run: ({ context }) => {
        console.log(`hello ${context.hello}`)
      },
      thenGoTo: StateOne,
    }),
  ],
}))
  1. Start your machine
ExampleMachine.start()
  1. Debug

You can see roughly what your machine is doing by setting the env var DEBUG_MEK=true.

Warning

This is a personal project that's pre-1.0.0. Any version can have a breaking change. If you feel like using this project anyway you should pin the version in your package.json to the latest version at the time you install it (ex "@tylerb/mek": "0.0.1", notice no ~ or ^ before the version :)