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

@webinar-geek/machine-component

v0.0.1

Published

A tool for creating react components which render based on the current state of an XState state machine

Readme

Machine Component

Installation

npm install @webinar-geek/machine-component

Motivation

When creating a react component which uses a state machine for conditional rendering based on it's states, you will have a series of if statements that for each state telling react what to render

const Component = ({ actorRef }) => {
  const state = useSelector(actorRef, (state) => state.value)

  if (state === "a") {
    return <div>A</div>
  } else if (state === "b") {
    return <div>B</div>
  } else if (state === "c") {
    return <div>C</div>
  }

  return <div>Default</div>
}

By using a createMachineComponent helper, you can do this in a more declarative way

import { createMachineComponent } from "@webinargeek/machine-component"

const Component = createMachineComponent<MyMachine>({
  states: {
    a: () => <div>A</div>,
    b: () => <div>B</div>,
    c: () => <div>C</div>,
  },
})

Usage

The createMachineComponent function takes a config object which mirrors the states of an xstate machine and assigns a component to any of them. This component will be rendered when an actor whose config is that machine is passed to it via props

import { createMachine } from "xstate"
import { useActorRef } from "@xstate/react"
import { createMachineComponent } from "@webinargeek/machine-component"

const myMachine = createMachine({
  initial: "a",
  states: {
    a: {
      on: {
        NEXT: "b",
      },
    },
    b: {
      on: {
        NEXT: "c",
      },
    },
    c: {
      on: {
        NEXT: "a",
      },
    },
  },
})

type MyMachine = typeof machine

const Component = createMachineComponent<MyMachine>({
  states: {
    a: () => <div>A</div>,
    b: () => <div>B</div>,
    c: () => <div>C</div>,
  },
})

const App = () => {
  const actorRef = useActorRef(myMachine)
  return <Component actorRef={actorRef} />
}

Layout components

A Component can be passed to the Component field of a parent state which will be rendered without being unmounted as the child states change.

The components defined in the child states will be passed into the children prop.

const Component = createMachineComponent<MyMachine>({
  states: {
    a: {
      Component: () => <div>A {children}</div>,
      states: {
        b: () => <div>B</div>,
        c: () => <div>C</div>,
      },
    },
    d: () => <div>D</div>,
  },
})

Prop forwarding

The second generic parameter of the createMachineComponent function is a props object which will be forwarded to all state components.

The state components will also receive the actorRef prop that was passed to the machine component.

const Component = createMachineComponent<MyMachine, { foo: string }>({
  states: {
    a: {
      Component: ({ foo }) => <div>A {foo}</div>,
    },
    b: ({ foo }) => <div>B {foo}</div>,
    c: ({ children, actorRef }) => {
      const context = useSelector(actorRef, (state) => state.context)
      return <div>C {children}</div>
    },
  },
})

const App = ({ children }) => {
  const actorRef = useActor(myMachine)
  return (
    <Component actorRef={actorRef} foo="bar">
      {children}
    </Component>
  )
}

Parallel states

TODO....