@specific.dev/spectest 0.35.1 → 0.36.0

package/dist/components/postgres.d.ts

@@ -1,3 +1,4 @@
+import type { ServiceSetupContext } from "../index.js";
 import { type SqlClient } from "../sql.js";
 export interface PostgresOptions {
     /** Image tag for the official `postgres` image. Default `"18-alpine"`.
@@ -32,6 +33,28 @@ export interface PostgresOptions {
     args?: string[];
     /** Extra environment variables forwarded to the container. */
     env?: Record<string, string>;
+    /**
+     * One-shot hook that runs after the ready probe passes, before any
+     * dependent service starts and before any test. This is where schema
+     * and seed data go: the daemon captures the result into the
+     * warm-template snapshot, so it never runs again on a warm start or a
+     * fork.
+     *
+     * The argument is the full test context plus this service's `name` and
+     * its {@link PostgresHelpers}, so the instrumented client is already
+     * built:
+     *
+     * ```ts
+     * db: postgres({
+     *   database: "todos", user: "todos", password: "todos",
+     *   setup: async ({ helpers }) => {
+     *     await helpers.client`CREATE TABLE todos (
+     *       id SERIAL PRIMARY KEY, text TEXT NOT NULL)`;
+     *   },
+     * }),
+     * ```
+     */
+    setup?: (args: ServiceSetupContext<PostgresHelpers>) => void | Promise<void>;
 }
 /** Helpers a `postgres(...)` service exposes on `ctx.svc.<name>`. */
 export interface PostgresHelpers {
@@ -67,6 +90,7 @@ export interface PostgresHelpers {
  * ```
  */
 export declare function postgres(opts: PostgresOptions): {
+    setup?: ((args: ServiceSetupContext<PostgresHelpers>) => void | Promise<void>) | undefined;
     env: {
         POSTGRES_DB: string;
         POSTGRES_USER: string;

package/dist/components/postgres.js

@@ -54,5 +54,10 @@ export function postgres(opts) {
                 `@${name}:${port}/${encodeURIComponent(opts.database)}`;
             return { client: new SQL(url, { label: name }) };
         },
+        // The user's hook, forwarded verbatim — postgres() declares none of
+        // its own. If it ever gains one, CHAIN the user's after it (the way
+        // `serviceGroup` chains a group hook after the primary part's) rather
+        // than letting either one win.
+        ...(opts.setup ? { setup: opts.setup } : {}),
     };
 }

package/dist/index.d.ts

@@ -455,8 +455,17 @@ export interface ServiceDefinition<H extends Record<string, any> = Record<string
 }
 /** A services map — what users pass to `environment.services`. Entries
  * can be plain `ServiceConfig` literals or `ServiceDefinition`s that
- * carry a `helpers` factory (e.g. what `postgres(...)` returns). */
-export type ServicesMap = Record<string, ServiceConfig>;
+ * carry a `helpers` factory (e.g. what `postgres(...)` returns).
+ *
+ * The entry type is `ServiceDefinition`, not `ServiceConfig`: at runtime
+ * the map really does hold `helpers`/`setup` (the daemon reads them off
+ * each entry), and both are optional, so every plain `ServiceConfig`
+ * still satisfies it. Narrowing this to `ServiceConfig` — the wire type,
+ * which by definition carries no functions — made the natural way to
+ * hoist a services map out of `index.ts` (`… satisfies ServicesMap`) fail
+ * the typecheck on any service declaring a hook, while the same literal
+ * written inline passed. */
+export type ServicesMap = Record<string, ServiceDefinition<any>>;
 /** Awaited return type of a service's `helpers` factory, or `never` if
  * the service doesn't ship one. */
 type HelpersOf<D> = D extends {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@specific.dev/spectest",
-  "version": "0.35.1",
+  "version": "0.36.0",
   "description": "Spectest SDK for defining test environments in TypeScript.",
   "type": "module",
   "main": "./dist/index.js",