emdash 1.1.0 → 1.3.0

package/dist/runner-J3Cj6DGk.d.mts

@@ -1,68 +0,0 @@
-import { t as Database } from "./types-ifgOkcBa.mjs";
-import { Kysely } from "kysely";
-import { Migrator } from "kysely/migration";
-
-//#region src/database/migrations/runner.d.ts
-/** Ordered names from the statically registered migration set. */
-declare const MIGRATION_NAMES: readonly string[];
-interface MigrationStatus {
-  applied: string[];
-  pending: string[];
-}
-interface ExactMigrationStatus {
-  knownApplied: string[];
-  pending: string[];
-  unknownApplied: string[];
-}
-interface MigrationOptions {
-  migrationTableSchema?: string;
-  /**
-   * Override how long to wait for a concurrent migrator to finish before
-   * giving up. Defaults to MIGRATION_RACE_WAIT_MS; tests shorten it so the
-   * give-up path doesn't take 10 seconds per case.
-   */
-  raceWaitMs?: number;
-}
-/**
- * Get migration status
- */
-declare function getMigrationStatus(db: Kysely<Database>, options?: MigrationOptions): Promise<MigrationStatus>;
-/**
- * Read exact migration status without invoking Kysely's migration
- * introspection. Registered names retain execution order; unknown database
- * records are sorted so reports remain stable across dialects.
- */
-declare function getExactMigrationStatus(db: Kysely<Database>, options?: MigrationOptions): Promise<ExactMigrationStatus>;
-/**
- * Run all pending migrations.
- *
- * Includes a fast-path: if the migration table already exists and contains
- * at least MIGRATION_COUNT rows, all migrations this build knows about have
- * been applied and we can skip the Kysely Migrator entirely. This avoids
- * the expensive `pragma_table_info` introspection that Kysely runs for
- * every table in the database (twice!) just to check if the migration
- * tables exist. On D1 with ~57 tables, that's ~116 queries saved per init.
- *
- * Concurrent-migration safety: the Kysely Migrator's `acquireMigrationLock`
- * is a no-op for SQLite, so two callers running this concurrently against the
- * same database will both try to apply pending migrations. (D1 and Postgres
- * take a lock, and the loser gets the busy error handled below.) SQLite
- * serializes the writes, but the loser still surfaces a
- * `UNIQUE constraint failed: _emdash_migrations.name` error. We treat that
- * specific error as benign: another caller is already applying the same
- * schema. We wait for the concurrent migrator to finish, then return
- * success. This matches the user-observable expectation that running
- * migrations twice in a row is a no-op.
- */
-declare function runMigrations(db: Kysely<Database>, options?: MigrationOptions): Promise<{
-  applied: string[];
-}>;
-/**
- * Rollback the last migration
- */
-declare function rollbackMigration(db: Kysely<Database>, options?: MigrationOptions): Promise<{
-  rolledBack: string | null;
-}>;
-//#endregion
-export { getMigrationStatus as a, getExactMigrationStatus as i, MIGRATION_NAMES as n, rollbackMigration as o, MigrationStatus as r, runMigrations as s, ExactMigrationStatus as t };
-//# sourceMappingURL=runner-J3Cj6DGk.d.mts.map

package/dist/runner-J3Cj6DGk.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"runner-J3Cj6DGk.d.mts","names":[],"sources":["../src/database/migrations/runner.ts"],"mappings":";;;;;;cAoMa,eAAA;AAAA,UAeI,eAAA;EAChB,OAAA;EACA,OAAA;AAAA;AAAA,UAGgB,oBAAA;EAChB,YAAA;EACA,OAAA;EACA,cAAA;AAAA;AAAA,UAuCgB,gBAAA;EAChB,oBAAA;EAyBS;;;;;EAnBT,UAAA;AAAA;;;AAmLD;iBAnKsB,kBAAA,CACrB,EAAA,EAAI,MAAA,CAAO,QAAA,GACX,OAAA,GAAU,gBAAA,GACR,OAAA,CAAQ,eAAA;;;;;;iBAgKW,uBAAA,CACrB,EAAA,EAAI,MAAA,CAAO,QAAA,GACX,OAAA,GAAU,gBAAA,GACR,OAAA,CAAQ,oBAAA;;;;;AAkDX;;;;;;;;;;;;;;;;;iBAAsB,aAAA,CACrB,EAAA,EAAI,MAAA,CAAO,QAAA,GACX,OAAA,GAAU,gBAAA,GACR,OAAA;EAAU,OAAA;AAAA;;;;iBA8DS,iBAAA,CACrB,EAAA,EAAI,MAAA,CAAO,QAAA,GACX,OAAA,GAAU,gBAAA,GACR,OAAA;EAAU,UAAA;AAAA"}