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

babystack

v0.1.0

Published

Real MySQL, fresh every run — a local baby of your production stack. Seeded, disposable, real backing services for tests + AI agents. The flagship: re-exports the API and ships the `baby` CLI.

Readme

babystack

Real MySQL, fresh every run — a local baby of your production stack.

Every test run and every AI-agent session gets its own private, seeded, disposable copy of the real services your app uses — spun up in Docker, injected as env vars, thrown away after. No shared dev DB, no mocks, no lifecycle code in your tests.

This is the flagship package: it re-exports the public API (defineConfig and the config types) and ships the baby CLI. For the Vitest test wedge you also install the scoped packages below.

Pre-alpha. Today babystack implements exactly one engine — real MySQL — delivered through Vitest and the baby CLI. Other engines (Postgres next, then Redis, S3/MinIO, the AWS tail via LocalStack) are on the roadmap.

Install

# the CLI (operator + AI-agent surface):
pnpm add -D babystack     # gives you the `baby` command

# the Vitest wedge (fresh, seeded, isolated real MySQL for your tests):
pnpm add -D @babystack/vitest     # one package — pulls the engine transitively

The baby CLI

baby doctor     # preflight: Node, a reachable Docker engine, your config
baby wake       # provision + seed a real MySQL and leave it running
eval "$(baby home)"   # export a DATABASE_URL for the running stack
baby reset      # reload a pristine DB from the baseline (the agent's undo)
baby sleep      # dispose this project's stack

An AI coding agent gets a real, disposable backend for a session and can baby reset between attempts — without ever touching your real dev/prod services.

The config

// babystack.config.ts
import { defineConfig } from 'babystack' // (or '@babystack/core')

export default defineConfig({
  services: {
    db: {
      engine: 'mysql',
      image: 'mysql:8.4',
      baseline: { build: ['pnpm db:migrate', 'pnpm db:seed'] },
    },
  },
})

Learn more

Full docs, the Vitest setup, and a runnable example app live in the repository: https://github.com/babystack/babystack. Licensed Apache-2.0.