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

@playfast/muxmaxing-config

v0.1.1

Published

Author API for muxmaxing.config.ts — a repo-committed hook bridge between the host device and muxmaxing work units: typed host-input collection plus Effect-native lifecycle hooks (machine created, new terminal, removed) with bash bridged into the unit.

Downloads

10,393

Readme

@playfast/muxmaxing-config

Author API for a repo-committed muxmaxing.config.ts — a hook bridge between the host device (the machine running mux) and a work unit (the pod/VM muxmaxing creates for your repo). Declare a typed hostInput payload, collect it on the host (env, CLIs, logins), and act on unit lifecycle moments with it. Hooks are Effect-native and run host-side in a Bun Worker, only for repos the user has explicitly approved.

Example — preconfigure the Doppler CLI in every work unit

// muxmaxing.config.ts (repo root, committed)
import { defineConfig } from '@playfast/muxmaxing-config'
import { Effect, Schema as S } from 'effect'

const TokenJson = S.parseJson(S.Struct({ key: S.String, slug: S.String }))

export default defineConfig({
  hostInput: S.Struct({ dopplerToken: S.String, tokenSlug: S.String }),

  // Runs ON THE HOST: mint an ephemeral read-only token with the user's own login.
  collectHostDeviceInput: ({ host, unit }) =>
    Effect.gen(function* () {
      const minted = yield* host.bash(
        `doppler configs tokens create mux-${unit.id} --project my-app --config dev --max-age 24h --json`,
      )
      const token = yield* S.decode(TokenJson)(minted.stdout)
      return { dopplerToken: token.key, tokenSlug: token.slug }
    }),

  // Runs when the unit is up: `ctx.unit.bash` execs INSIDE the unit.
  onWorkUnitMachineCreated: (ctx) =>
    Effect.gen(function* () {
      yield* ctx.unit.bash(
        `doppler configure set token ${ctx.hostInput.dopplerToken} --scope ${ctx.unit.workspaceFolder}`,
      )
      yield* ctx.log('doppler CLI preconfigured')
    }),

  // Runs at teardown ON THE HOST: revoke exactly the token this unit was minted.
  onWorkUnitRemoved: (ctx) =>
    ctx.host.bash(
      `doppler configs tokens revoke --slug ${ctx.hostInput.tokenSlug} --project my-app --config dev`,
    ),
})

Contract

  • hostInput — an Effect Schema; its encoded side must be plain JSON (it crosses the worker boundary and is cached memory-only by the engine between hooks).
  • collectHostDeviceInput(ctx) — runs once per unit on the host; produces the payload.
  • onWorkUnitMachineCreated(ctx) / onNewTerminal(ctx)ctx.unit.bash execs in the unit, ctx.host.bash on the host, ctx.log writes to the unit's creation pane.
  • onWorkUnitRemoved(ctx) — host-side cleanup; the unit may already be gone (no unit bash).
  • A bash result is { stdout, stderr, exitCode }; a non-zero exit is not an error — only a transport failure fails the Effect.

Trust model: hooks run on the host in a Bun Worker — a thread boundary, not a security sandbox. muxmaxing runs them only for repos the user approved (Settings → Hooks).