@zeroxsolutions/db 9.3.5 → 9.4.0

package/CHANGELOG.md

@@ -1,3 +1,14 @@
+## 9.4.0 (2026-10-14)
+
+### 🚀 Features
+
+- **db:** export the forced container remove from its own subpath ([fade0ea](https://github.com/zeroxsolutions/zeroxsolutions/commit/fade0ea))
+
+### ❤️ Thank You
+
+- Claude Opus 5.5
+- Lương Văn Tú
+
 ## 9.3.5 (2026-10-12)
 
 ### 🩹 Fixes

package/README.md

@@ -39,6 +39,7 @@ declares `"."`, but no `src/index.ts` exists for the build to emit it from, so
 | `@zeroxsolutions/db/d1`  | Cloudflare D1 (SQLite) entity, repository, unit of work, outbox, and types |
 | `@zeroxsolutions/db/utils` | Filter and order builders, `TableQuery` and the relational-read builder, the field-whitelist guard, the filter-value schema + operator enum, omit masks, pagination constants |
 | `@zeroxsolutions/db/testing` | A throwaway Postgres container carrying your schema, on the engine you name, plus the container timeout and a fake uuid v7 |
+| `@zeroxsolutions/db/containers` | The forced remove that tears down a container you started yourself |
 
 ---
 
@@ -525,6 +526,25 @@ typecheck failure rather than a suite that quietly passed on a major you do not
 | `CONTAINER_TIMEOUT_MS` | 180s, for the hook that starts a container: an image pull on a cold machine outruns vitest's 5s default |
 | `fakeUuidV7` | Random bits in a v7 layout: it passes a v7 check, and is not time-ordered like a minted id |
 
+### A container you started yourself
+
+A global setup that starts its own container, to migrate a template or several databases, tears it down
+with `removeContainer` from `@zeroxsolutions/db/containers`, not with the container's `stop()`:
+
+```ts
+import { removeContainer } from '@zeroxsolutions/db/containers';
+
+const container = await new PostgreSqlContainer(image).start();
+// ...
+return () => removeContainer(container);
+```
+
+`stop()` sends a stop and then a separate remove, and on a loaded host the daemon answers that remove
+with 409 "container is running", failing a suite whose every case passed. `removeContainer` is one forced
+remove, volumes included, and it is what `startDisposablePostgres`'s `stop()` calls. It rejects for a
+container the daemon no longer knows, so a teardown that runs twice shows. This subpath imports nothing
+but `@testcontainers/postgresql`, so an e2e project that installs no `drizzle-kit` can use it.
+
 ---
 
 ## Building

package/dist/containers/index.d.ts

@@ -0,0 +1,2 @@
+export * from './remove-container.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/containers/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/containers/index.ts"],"names":[],"mappings":"AAAA,cAAc,uBAAuB,CAAC"}

package/dist/containers/index.js

@@ -0,0 +1 @@
+export * from './remove-container.js';

package/dist/containers/remove-container.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Removes `container` and its volumes in one forced call, which the daemon carries out as a kill and a
+ * removal together. The container's own stop sends a stop and then a remove, and on a loaded host that
+ * remove answered 409 "container is running", failing a suite whose every case had passed
+ * (testcontainers@12.1.0, Docker Desktop 29).
+ * @param container - a container started through `@testcontainers/postgresql`.
+ * @throws whatever the daemon answers, including that it knows no such container, so a second teardown
+ * of the same container shows.
+ */
+export declare function removeContainer(container: {
+    getId(): string;
+}): Promise<void>;
+//# sourceMappingURL=remove-container.d.ts.map

package/dist/containers/remove-container.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"remove-container.d.ts","sourceRoot":"","sources":["../../src/containers/remove-container.ts"],"names":[],"mappings":"AAOA;;;;;;;;GAQG;AACH,wBAAsB,eAAe,CAAC,SAAS,EAAE;IAAE,KAAK,IAAI,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAGnF"}

package/dist/containers/remove-container.js

@@ -0,0 +1,24 @@
+import { createRequire } from 'node:module';
+/**
+ * Removes `container` and its volumes in one forced call, which the daemon carries out as a kill and a
+ * removal together. The container's own stop sends a stop and then a remove, and on a loaded host that
+ * remove answered 409 "container is running", failing a suite whose every case had passed
+ * (testcontainers@12.1.0, Docker Desktop 29).
+ * @param container - a container started through `@testcontainers/postgresql`.
+ * @throws whatever the daemon answers, including that it knows no such container, so a second teardown
+ * of the same container shows.
+ */
+export async function removeContainer(container) {
+    const runtime = await containerRuntime();
+    await runtime.container.getById(container.getId()).remove({ force: true, v: true });
+}
+/**
+ * The runtime client of the testcontainers that `@testcontainers/postgresql` itself runs on. It is
+ * resolved from that package rather than declared here, so a consumer installs nothing beyond the peer it
+ * already has, and the client is the one the container was started through.
+ */
+function containerRuntime() {
+    const fromPostgres = createRequire(createRequire(import.meta.url).resolve('@testcontainers/postgresql'));
+    const { getContainerRuntimeClient } = fromPostgres('testcontainers');
+    return getContainerRuntimeClient();
+}

package/dist/testing/disposable-postgres.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"disposable-postgres.d.ts","sourceRoot":"","sources":["../../src/testing/disposable-postgres.ts"],"names":[],"mappings":"AAGA,OAAO,EAAW,KAAK,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AAG3E,2FAA2F;AAC3F,eAAO,MAAM,oBAAoB,SAAU,CAAC;AAE5C,8FAA8F;AAC9F,MAAM,WAAW,kBAAkB,CAAC,OAAO,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IACzE,EAAE,EAAE,kBAAkB,CAAC,OAAO,CAAC,CAAC;IAChC;;;OAGG;IACH,gBAAgB,EAAE,MAAM,CAAC;IACzB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC,CAAC;CACvB;AAED;;;;;;;GAOG;AACH,wBAAsB,uBAAuB,CAAC,OAAO,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EACnF,MAAM,EAAE,OAAO,EACf,KAAK,EAAE,MAAM,GACZ,OAAO,CAAC,kBAAkB,CAAC,OAAO,CAAC,CAAC,CAqBtC"}
+{"version":3,"file":"disposable-postgres.d.ts","sourceRoot":"","sources":["../../src/testing/disposable-postgres.ts"],"names":[],"mappings":"AAEA,OAAO,EAAW,KAAK,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AAI3E,2FAA2F;AAC3F,eAAO,MAAM,oBAAoB,SAAU,CAAC;AAE5C,8FAA8F;AAC9F,MAAM,WAAW,kBAAkB,CAAC,OAAO,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IACzE,EAAE,EAAE,kBAAkB,CAAC,OAAO,CAAC,CAAC;IAChC;;;OAGG;IACH,gBAAgB,EAAE,MAAM,CAAC;IACzB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC,CAAC;CACvB;AAED;;;;;;;GAOG;AACH,wBAAsB,uBAAuB,CAAC,OAAO,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EACnF,MAAM,EAAE,OAAO,EACf,KAAK,EAAE,MAAM,GACZ,OAAO,CAAC,kBAAkB,CAAC,OAAO,CAAC,CAAC,CAiBtC"}

package/dist/testing/disposable-postgres.js

@@ -1,8 +1,8 @@
-import { createRequire } from 'node:module';
 import { PostgreSqlContainer } from '@testcontainers/postgresql';
 import { generateDrizzleJson, generateMigration } from 'drizzle-kit/api';
 import { drizzle } from 'drizzle-orm/postgres-js';
 import postgres from 'postgres';
+import { removeContainer } from '../containers/index.js';
 /** Pulling the image on a cold machine costs far more than vitest's 5s default timeout. */
 export const CONTAINER_TIMEOUT_MS = 180_000;
 /**
@@ -27,24 +27,10 @@ export async function startDisposablePostgres(schema, image) {
         connectionString,
         async stop() {
             await client.end();
-            // One forced remove, which the daemon carries out as a kill and a removal together. The container's
-            // own stop sends a stop and then a remove, and on a loaded host that remove answered 409 "container is
-            // running", failing a suite whose every case had passed (testcontainers@12.1.0, Docker Desktop 29).
-            const runtime = await containerRuntime();
-            await runtime.container.getById(container.getId()).remove({ force: true, v: true });
+            await removeContainer(container);
         },
     };
 }
-/**
- * The runtime client of the testcontainers that `@testcontainers/postgresql` itself runs on. It is
- * resolved from that package rather than declared here, so a consumer installs nothing beyond the peer it
- * already has, and the client is the one the container was started through.
- */
-function containerRuntime() {
-    const fromPostgres = createRequire(createRequire(import.meta.url).resolve('@testcontainers/postgresql'));
-    const { getContainerRuntimeClient } = fromPostgres('testcontainers');
-    return getContainerRuntimeClient();
-}
 /**
  * Prints a server WARNING as one line and drops every lower severity. Left to its default, postgres.js
  * prints each notice as a raw object, and a full-text search for a stop word alone raises two per

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zeroxsolutions/db",
-  "version": "9.3.5",
+  "version": "9.4.0",
   "description": "Generic Drizzle toolkit - the id column and audit timestamps a table takes, a base repository, the unit-of-work and transactional outbox impls, and the filter/sort/pagination query helpers, for PostgreSQL (postgres-js) and Cloudflare D1; ships no domain schema. Shared across ZeroXSolutions services.",
   "private": false,
   "type": "module",
@@ -32,6 +32,11 @@
       "types": "./dist/testing/index.d.ts",
       "import": "./dist/testing/index.js",
       "default": "./dist/testing/index.js"
+    },
+    "./containers": {
+      "types": "./dist/containers/index.d.ts",
+      "import": "./dist/containers/index.js",
+      "default": "./dist/containers/index.js"
     }
   },
   "dependencies": {