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

mini-machines

v2.0.1

Published

Simple & typesafe client-server communication

Downloads

20

Readme

mini machines

Installation

mini-machines requires TypeScript ≥ 4.1 for Template Literal Types and node ≥ 12 for async functions.

$ npm install mini-machines

Guide

Define machines on the server

import * as m from "./server"

m.router({
  products: m.machine({
    resolve: async () => {
      let products = await get_products()
      return { products }
    },
  }),
  product: m.machine({
    input: (raw) => {
      return validate_input(raw)
    },
    resolve: async ({ input }) => {
      let product = await get_product(input)
      return { product }
    },
  }),
})

Use contexts to create route guards

m.router({
  login: m.machine({
    input: (raw) => {
      return validate_input(raw)
    },
    resolve: async ({ input, cookies }) => {
      let session = await create_session(input)
      cookies.set("session", session)
      return { session }
    },
  }),
  user: m
    .context(async ({ cookies }) => {
      let user = await get_user(cookies.get("session"))
      if (!user) throw new Unauthorized("Session expired")
      return { user }
    })
    .router({
      profile: m.machine({
        resolve: async ({ context }) => {
          let profile = await get_profile(context.user)
          return { profile }
        },
      }),
    }),
})

Turn your machine into a server handler

m.create({
  router,
  prefix: "/",
  on_error: ({ path, error }) => {
    if (error instanceof PasswordTooShort) {
      return new m.MachineError({
        path,
        status: 401,
        message: '"password" must be at least 4 characters',
        output: {
          type: "validation",
          field: "password",
          error: '"password" must be at least 4 characters',
        },
      })
    } else {
      console.error("Unexpected error: ", error)
    }
  },
})

Communicate on the client

import { create } from "mini-machines/client"
import type { routes } from "./server"

let client = create<typeof routes>({ url: "/" })
let user = await client("login", { username, password })
let profile = await client("user:profile")