supabase-test 0.4.2 → 0.4.4

package/README.md

@@ -18,7 +18,7 @@
 
 `supabase-test` is a Supabase-optimized version of [`pgsql-test`](https://www.npmjs.com/package/pgsql-test) with Supabase defaults baked in. It provides instant, isolated PostgreSQL databases for testing with automatic transaction rollbacks, context switching, and clean seeding — configured for Supabase's local development environment. It's also great for GitHub Actions and CI/CD testing.
 
-Explore a full working example (including GitHub Actions CI/CD) in the [`supabase-test-suite`](https://github.com/constructive-iosupabase-test-suite) repo.
+Explore a full working example (including GitHub Actions CI/CD) in the [`supabase-test-suite`](https://github.com/constructive-io/supabase-test-suite) repo.
 
 ## Install
 
@@ -54,7 +54,7 @@ npm install supabase-test
    * [Programmatic Seeding](#-programmatic-seeding)
    * [CSV Seeding](#️-csv-seeding)
    * [JSON Seeding](#️-json-seeding)
-   * [Seeding](#-launchql-seeding)
+   * [Seeding](#-pgpm-seeding)
 7. [`getConnections() Options` ](#getconnections-options)
 8. [Disclaimer](#disclaimer)
 
@@ -235,9 +235,9 @@ This array lets you fully customize how your test database is seeded. You can co
 * [`seed.fn()`](#-programmatic-seeding) – Run JavaScript/TypeScript logic to programmatically insert data
 * [`seed.csv()`](#️-csv-seeding) – Load tabular data from CSV files
 * [`seed.json()`](#️-json-seeding) – Use in-memory objects as seed data
-* [`seed.launchql()`](#-launchql-seeding) – Apply a LaunchQL project or set of packages (compatible with sqitch)
+* [`seed.pgpm()`](#-pgpm-seeding) – Apply a PGPM project or set of packages (compatible with sqitch)
 
-> ✨ **Default Behavior:** If no `SeedAdapter[]` is passed, LaunchQL seeding is assumed. This makes `supabase-test` zero-config for LaunchQL-based projects.
+> ✨ **Default Behavior:** If no `SeedAdapter[]` is passed, pgpm seeding is assumed. This makes `supabase-test` zero-config for pgpm-based projects.
 
 This composable system allows you to mix-and-match data setup strategies for flexible, realistic, and fast database tests.
 
@@ -259,7 +259,7 @@ await db.loadCsv({ 'users': '/path/to/users.csv' });
 await db.loadSql(['/path/to/schema.sql']);
 ```
 
-> **Note:** `loadCsv()` and `loadLaunchql()` do not apply RLS context (PostgreSQL limitation). Use `loadJson()` or `loadSql()` for RLS-aware seeding.
+> **Note:** `loadCsv()` and `loadPpgm()` do not apply RLS context (PostgreSQL limitation). Use `loadJson()` or `loadSql()` for RLS-aware seeding.
 
 ### 🔌 SQL File Seeding
 
@@ -500,32 +500,32 @@ it('has loaded rows', async () => {
 
 </details>
 
-## 🚀 LaunchQL Seeding
+## 🚀 pgpm Seeding
 
 **Zero Configuration (Default):**
 ```ts
-// LaunchQL migrate is used automatically
+// pgpm migrate is used automatically
 const { db, teardown } = await getConnections();
 ```
 
 **Adapter Pattern (Custom Path):**
 ```ts
 const { db, teardown } = await getConnections({}, [
-  seed.launchql('/path/to/launchql', true) // with cache
+  seed.pgpm('/path/to/your-pgpm-workspace', true) // with cache
 ]);
 ```
 
 **Direct Load Method:**
 ```ts
-await db.loadLaunchql('/path/to/launchql', true); // with cache
+await db.loadPgpm('/path/to/your-pgpm-workspace', true); // with cache
 ```
 
-> **Note:** LaunchQL deployment has its own client handling and does not apply RLS context.
+> **Note:** pgpm deployment has its own client handling and does not apply RLS context.
 
 <details>
 <summary>Full example</summary>
 
-If your project uses LaunchQL modules with a precompiled `launchql.plan`, you can use `supabase-test` with **zero configuration**. Just call `getConnections()` — and it *just works*:
+If your project uses pgpm modules with a precompiled `pgpm.plan`, you can use `supabase-test` with **zero configuration**. Just call `getConnections()` — and it *just works*:
 
 ```ts
 import { getConnections } from 'supabase-test';
@@ -533,50 +533,39 @@ import { getConnections } from 'supabase-test';
 let db, teardown;
 
 beforeAll(async () => {
-  ({ db, teardown } = await getConnections()); // LaunchQL module is deployed automatically
+  ({ db, teardown } = await getConnections()); // pgpm module is deployed automatically
 });
 ```
 
-LaunchQL uses Sqitch-compatible syntax with a TypeScript-based migration engine. By default, `supabase-test` automatically deploys any LaunchQL module found in the current working directory (`process.cwd()`).
+pgpm uses Sqitch-compatible syntax with a TypeScript-based migration engine. By default, `supabase-test` automatically deploys any pgpm module found in the current working directory (`process.cwd()`).
 
-To specify a custom path to your LaunchQL module, use `seed.launchql()` explicitly:
+To specify a custom path to your pgpm module, use `seed.pgpm()` explicitly:
 
 ```ts
 import path from 'path';
 import { getConnections, seed } from 'supabase-test';
 
-const cwd = path.resolve(__dirname, '../path/to/launchql');
+const cwd = path.resolve(__dirname, '../path/to/pgpm-workspace');
 
 beforeAll(async () => {
   ({ db, teardown } = await getConnections({}, [
-    seed.launchql(cwd)
+    seed.pgpm(cwd)
   ]));
 });
 ```
 
 </details>
 
-## Why LaunchQL's Approach?
+## Why PGPM's Approach?
 
-LaunchQL provides the best of both worlds:
+pgpm provides the best of both worlds:
 
 1. **Sqitch Compatibility**: Keep your familiar Sqitch syntax and migration approach
 2. **TypeScript Performance**: Our TS-rewritten deployment engine delivers up to 10x faster schema deployments
 3. **Developer Experience**: Tight feedback loops with near-instant schema setup for tests
 4. **CI Optimization**: Dramatically reduced test suite run times with optimized deployment
 
-By maintaining Sqitch compatibility while supercharging performance, LaunchQL enables you to keep your existing migration patterns while enjoying the speed benefits of our TypeScript engine.
-
-## Why LaunchQL's Approach?
-
-LaunchQL provides the best of both worlds:
-
-1. **Sqitch Compatibility**: Keep your familiar Sqitch syntax and migration approach
-2. **TypeScript Performance**: Our TS-rewritten deployment engine delivers up to 10x faster schema deployments
-3. **Developer Experience**: Tight feedback loops with near-instant schema setup for tests
-4. **CI Optimization**: Dramatically reduced test suite run times with optimized deployment
-
-By maintaining Sqitch compatibility while supercharging performance, LaunchQL enables you to keep your existing migration patterns while enjoying the speed benefits of our TypeScript engine.
+By maintaining Sqitch compatibility while supercharging performance, pgpm enables you to keep your existing migration patterns while enjoying the speed benefits of our TypeScript engine.
 
 ## `getConnections` Options
 
@@ -689,18 +678,18 @@ Common issues and solutions for pgpm, PostgreSQL, and testing.
 
 ### 🔁 Streaming & Uploads
 
+* [etag-hash](https://github.com/constructive-io/constructive/tree/main/packages/etag-hash): **🏷️ S3-compatible ETags** created by streaming and hashing file uploads in chunks.
+* [etag-stream](https://github.com/constructive-io/constructive/tree/main/packages/etag-stream): **🔄 ETag computation** via Node stream transformer during upload or transfer.
+* [uuid-hash](https://github.com/constructive-io/constructive/tree/main/packages/uuid-hash): **🆔 Deterministic UUIDs** generated from hashed content, great for deduplication and asset referencing.
+* [uuid-stream](https://github.com/constructive-io/constructive/tree/main/packages/uuid-stream): **🌊 Streaming UUID generation** based on piped file content—ideal for upload pipelines.
 * [launchql/s3-streamer](https://github.com/constructive-io/constructive/tree/main/packages/s3-streamer): **📤 Direct S3 streaming** for large files with support for metadata injection and content validation.
-* [launchql/etag-hash](https://github.com/constructive-io/constructive/tree/main/packages/etag-hash): **🏷️ S3-compatible ETags** created by streaming and hashing file uploads in chunks.
-* [launchql/etag-stream](https://github.com/constructive-io/constructive/tree/main/packages/etag-stream): **🔄 ETag computation** via Node stream transformer during upload or transfer.
-* [launchql/uuid-hash](https://github.com/constructive-io/constructive/tree/main/packages/uuid-hash): **🆔 Deterministic UUIDs** generated from hashed content, great for deduplication and asset referencing.
-* [launchql/uuid-stream](https://github.com/constructive-io/constructive/tree/main/packages/uuid-stream): **🌊 Streaming UUID generation** based on piped file content—ideal for upload pipelines.
 * [launchql/upload-names](https://github.com/constructive-io/constructive/tree/main/packages/upload-names): **📂 Collision-resistant filenames** utility for structured and unique file names for uploads.
 
 ### 🧰 CLI & Codegen
 
 * [pgpm](https://github.com/constructive-io/constructive/tree/main/packages/pgpm): **🖥️ PostgreSQL Package Manager** for modular Postgres development. Works with database workspaces, scaffolding, migrations, seeding, and installing database packages.
 * [@launchql/cli](https://github.com/constructive-io/constructive/tree/main/packages/cli): **🖥️ Command-line toolkit** for managing LaunchQL projects—supports database scaffolding, migrations, seeding, code generation, and automation.
-* [constructive-io/constructive-gen](https://github.com/constructive-io/constructive/tree/main/packages/launchql-gen): **✨ Auto-generated GraphQL** mutations and queries dynamically built from introspected schema data.
+* [launchql-gen](https://github.com/constructive-io/constructive/tree/main/packages/launchql-gen): **✨ Auto-generated GraphQL** mutations and queries dynamically built from introspected schema data.
 * [@launchql/query-builder](https://github.com/constructive-io/constructive/tree/main/packages/query-builder): **🏗️ SQL constructor** providing a robust TypeScript-based query builder for dynamic generation of `SELECT`, `INSERT`, `UPDATE`, `DELETE`, and stored procedure calls—supports advanced SQL features like `JOIN`, `GROUP BY`, and schema-qualified queries.
 * [@launchql/query](https://github.com/constructive-io/constructive/tree/main/packages/query): **🧩 Fluent GraphQL builder** for PostGraphile schemas. ⚡ Schema-aware via introspection, 🧩 composable and ergonomic for building deeply nested queries.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supabase-test",
-  "version": "0.4.2",
+  "version": "0.4.4",
   "author": "Interweb <developers@interweb.io>",
   "description": "supabase-test offers isolated, role-aware, and rollback-friendly PostgreSQL environments for integration tests with Supabase defaults baked in",
   "main": "index.js",
@@ -52,12 +52,12 @@
     "test:watch": "jest --watch"
   },
   "dependencies": {
-    "@pgpmjs/types": "^2.12.0",
-    "pg-env": "^1.2.1",
-    "pgsql-test": "^2.16.2"
+    "@pgpmjs/types": "^2.12.2",
+    "pg-env": "^1.2.2",
+    "pgsql-test": "^2.17.0"
   },
   "devDependencies": {
     "makage": "^0.1.8"
   },
-  "gitHead": "0f810b087435df60801bfa63d4f780e95acb6d02"
+  "gitHead": "4326e2092d0c57901e898560974d502d626c42cb"
 }