@babystack/vitest
v0.1.0
Published
babystack Vitest integration — globalSetup/setupFiles that provision the seeded stack and inject env.
Readme
@babystack/vitest
The Vitest integration for babystack — fresh, seeded, isolated real MySQL for your integration tests, with zero test-code changes.
Add three lines to vitest.config.ts and your tests just read process.env.DATABASE_URL, exactly like
production. One mysqld container is provisioned once and seeded into a baseline; each Vitest worker gets
its own fresh database loaded from it (keyed by VITEST_POOL_ID), so tests run in parallel against isolated
real databases.
// vitest.config.ts
import { defineConfig } from 'vitest/config'
export default defineConfig({
test: {
globalSetup: '@babystack/vitest/global-setup',
setupFiles: ['@babystack/vitest/setup'],
pool: 'forks',
},
})pnpm add -D @babystack/vitest # one package — pulls the engine (core + mysql + docker) transitivelyYour babystack.config.ts imports defineConfig from @babystack/vitest (re-exported here, so this is the
only package you install for tests). Requires a running Docker engine. For the config format, isolation semantics, and a runnable example, see
the babystack repository. Licensed Apache-2.0.
