Give each checkout its own test database

At a glanceCopy Anchor Link

• Who: Developers whose test suites drop and recreate a Postgres database.
• What: Derive a stable per-checkout database name and refuse unsafe names before they reach DROP.
• Use when: When several checkouts or worktrees run tests against one Postgres server.
• Avoid when: For production database naming, or when each test run gets a throwaway container.

InstallCopy Anchor Link

pnpm add @zedtech/zedkit-server

Latest: 1.1.0 (via changesets).

ExampleCopy Anchor Link

import { databaseNameFromUrl, suffixedDatabaseUrl } from "@zedtech/zedkit-server";
const url = suffixedDatabaseUrl(process.env.TEST_DATABASE_URL!, process.cwd());
const name = databaseNameFromUrl(url); // safe to interpolate into DROP/CREATE

Wraps: (none)