DocsRecipes
Local development
Use seedkit's `--env` flag to populate `.env.local` so your dev server picks it up automatically.
The --env flag on seedkit new writes DATABASE_URL=... to your project's .env.local. Most JS/TS dev servers read that file on startup — Next.js, Remix, Bun, SvelteKit, and friends.
One command
npx seedkit-cli new --schema prisma/schema.prisma --seed dev --env
✓ Wrote DATABASE_URL to .env.local
Then:
npm run dev
Your app picks up the new connection string and starts querying real Postgres data.
Re-using the same fixture
Because we passed --seed dev, subsequent runs hit the cache and replay byte-identically:
seedkit revive dev --env
# Same data as last time. New connection string. Wrote to .env.local.
This is useful when you accidentally psql your way into corrupting the DB and want to start over with the same baseline.
.env.local merging
Existing keys in .env.local are preserved. We replace DATABASE_URL if it's there, append it if not. We never touch other vars.