@pgpmjs/pglite-adapter 0.1.0

package/LICENSE

@@ -0,0 +1,23 @@
+The MIT License (MIT)
+
+Copyright (c) 2025 Dan Lynch <pyramation@gmail.com>
+Copyright (c) 2025 Constructive <developers@constructive.io>
+Copyright (c) 2020-present, Interweb, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,125 @@
+# @pgpmjs/pglite-adapter
+
+A PGlite driver for pgpm. It registers an **in-process** [PGlite](https://github.com/electric-sql/pglite)
+instance (WASM Postgres) as the `pg-cache` pool factory, so the **unmodified**
+pgpm engine deploys, verifies, and reverts migrations against PGlite with **no
+Postgres server and no socket**.
+
+All `@electric-sql/pglite*` dependencies live here — `@pgpmjs/core`, `pg-cache`,
+and `pgsql-test` never import them.
+
+## How it works
+
+pgpm's engine only needs a node-`pg`-shaped pool (`query` / `connect` / `end`).
+Step 1 added a driver seam in `pg-cache` (`registerPgPoolFactory`). This package
+implements that seam against PGlite's JS API:
+
+- parameterized queries → `db.query` (extended protocol)
+- parameterless / multi-statement SQL (pgpm's bootstrap) → `db.exec`
+
+Because PGlite is a single in-process session, both `pool.query` and the client
+returned by `connect()` share one session — so pgpm's transactional deploy works
+without the socket PoC's `useTransaction: false` workaround.
+
+## Usage
+
+```ts
+import { PgpmMigrate } from '@pgpmjs/core';
+import { registerPglite } from '@pgpmjs/pglite-adapter';
+
+const { db, close } = await registerPglite();
+
+const migrate = new PgpmMigrate({ database: 'postgres' /* ...pg config */ });
+await migrate.deploy({ modulePath: './my-module' });
+await migrate.verify({ modulePath: './my-module' });
+
+await close(); // restores the previous factory and closes PGlite
+```
+
+### Extensions
+
+pgpm's `cleanSql` strips `CREATE EXTENSION` from migrations, so extensions are
+provisioned out-of-band — register the WASM extension at construction and run
+`CREATE EXTENSION` at bootstrap:
+
+```ts
+import { vector } from '@electric-sql/pglite-pgvector';
+
+const { db, close } = await registerPglite({
+  extensions: { vector },
+  extensionSql: ['CREATE EXTENSION IF NOT EXISTS vector;']
+});
+```
+
+---
+
+## Education and Tutorials
+
+ 1. 🚀 [Quickstart: Getting Up and Running](https://constructive.io/learn/quickstart)
+Get started with modular databases in minutes. Install prerequisites and deploy your first module.
+
+ 2. 📦 [Modular PostgreSQL Development with Database Packages](https://constructive.io/learn/modular-postgres)
+Learn to organize PostgreSQL projects with pgpm workspaces and reusable database modules.
+
+ 3. ✏️ [Authoring Database Changes](https://constructive.io/learn/authoring-database-changes)
+Master the workflow for adding, organizing, and managing database changes with pgpm.
+
+ 4. 🧪 [End-to-End PostgreSQL Testing with TypeScript](https://constructive.io/learn/e2e-postgres-testing)
+Master end-to-end PostgreSQL testing with ephemeral databases, RLS testing, and CI/CD automation.
+
+ 5. ⚡ [Supabase Testing](https://constructive.io/learn/supabase)
+Use TypeScript-first tools to test Supabase projects with realistic RLS, policies, and auth contexts.
+
+ 6. 💧 [Drizzle ORM Testing](https://constructive.io/learn/drizzle-testing)
+Run full-stack tests with Drizzle ORM, including database setup, teardown, and RLS enforcement.
+
+ 7. 🔧 [Troubleshooting](https://constructive.io/learn/troubleshooting)
+Common issues and solutions for pgpm, PostgreSQL, and testing.
+
+## Related Constructive Tooling
+
+### 📦 Package Management
+
+* [pgpm](https://github.com/constructive-io/constructive/tree/main/pgpm/pgpm): **🖥️ PostgreSQL Package Manager** for modular Postgres development. Works with database workspaces, scaffolding, migrations, seeding, and installing database packages.
+
+### 🧪 Testing
+
+* [pgsql-test](https://github.com/constructive-io/constructive/tree/main/postgres/pgsql-test): **📊 Isolated testing environments** with per-test transaction rollbacks—ideal for integration tests, complex migrations, and RLS simulation.
+* [pgsql-seed](https://github.com/constructive-io/constructive/tree/main/postgres/pgsql-seed): **🌱 PostgreSQL seeding utilities** for CSV, JSON, SQL data loading, and pgpm deployment.
+* [supabase-test](https://github.com/constructive-io/constructive/tree/main/postgres/supabase-test): **🧪 Supabase-native test harness** preconfigured for the local Supabase stack—per-test rollbacks, JWT/role context helpers, and CI/GitHub Actions ready.
+* [graphile-test](https://github.com/constructive-io/constructive/tree/main/graphile/graphile-test): **🔐 Authentication mocking** for Graphile-focused test helpers and emulating row-level security contexts.
+* [pg-query-context](https://github.com/constructive-io/constructive/tree/main/postgres/pg-query-context): **🔒 Session context injection** to add session-local context (e.g., `SET LOCAL`) into queries—ideal for setting `role`, `jwt.claims`, and other session settings.
+
+### 🧠 Parsing & AST
+
+* [pgsql-parser](https://www.npmjs.com/package/pgsql-parser): **🔄 SQL conversion engine** that interprets and converts PostgreSQL syntax.
+* [libpg-query-node](https://www.npmjs.com/package/libpg-query): **🌉 Node.js bindings** for `libpg_query`, converting SQL into parse trees.
+* [pg-proto-parser](https://www.npmjs.com/package/pg-proto-parser): **📦 Protobuf parser** for parsing PostgreSQL Protocol Buffers definitions to generate TypeScript interfaces, utility functions, and JSON mappings for enums.
+* [@pgsql/enums](https://www.npmjs.com/package/@pgsql/enums): **🏷️ TypeScript enums** for PostgreSQL AST for safe and ergonomic parsing logic.
+* [@pgsql/types](https://www.npmjs.com/package/@pgsql/types): **📝 Type definitions** for PostgreSQL AST nodes in TypeScript.
+* [@pgsql/utils](https://www.npmjs.com/package/@pgsql/utils): **🛠️ AST utilities** for constructing and transforming PostgreSQL syntax trees.
+
+### 📚 Documentation & Skills
+
+* [constructive-skills](https://github.com/constructive-io/constructive-skills): **📖 Platform documentation and AI agent skills** — feature catalog, blueprint reference, SDK guides (i18n, billing, limits, events, uploads, security, entities, search, AI), and deployment guides.
+
+Install skills for AI coding agents:
+
+```bash
+# All platform skills (security, blueprints, codegen, billing, etc.)
+npx skills add constructive-io/constructive-skills
+
+# Individual repo skills (pgpm, testing, CLI, search, etc.)
+npx skills add https://github.com/constructive-io/constructive --skill pgpm
+npx skills add https://github.com/constructive-io/constructive --skill constructive-testing
+```
+
+## Credits
+
+**🛠 Built by the [Constructive](https://constructive.io) team — creators of modular Postgres tooling for secure, composable backends. If you like our work, contribute on [GitHub](https://github.com/constructive-io).**
+
+## Disclaimer
+
+AS DESCRIBED IN THE LICENSES, THE SOFTWARE IS PROVIDED "AS IS", AT YOUR OWN RISK, AND WITHOUT WARRANTIES OF ANY KIND.
+
+No developer or entity involved in creating this software will be liable for any claims or damages whatsoever associated with your use, inability to use, or your interaction with other users of the code, including any direct, indirect, incidental, special, exemplary, punitive or consequential damages, or loss of profits, cryptocurrencies, tokens, or anything else of value.

package/client.d.ts

@@ -0,0 +1,21 @@
+import type { PGlite } from '@electric-sql/pglite';
+import { type PgResultLike } from './runner';
+/**
+ * The minimal node-`pg` `Client` surface that `pgsql-client`'s `PgClient` uses:
+ * `connect()`, `query()` and `end()`. A real `pg.Client` structurally satisfies
+ * it, so registering a factory that returns this is transparent to consumers.
+ */
+export interface QueryablePgClient {
+    connect(): Promise<void>;
+    query(text: any, values?: any[]): Promise<PgResultLike>;
+    end(): Promise<void>;
+}
+/**
+ * Build a `pg.Client`-shaped object backed by an existing PGlite instance.
+ *
+ * Every client returned for the same instance shares that single in-process
+ * session, so transaction control (`BEGIN`/`SAVEPOINT`/`ROLLBACK`/`COMMIT`) is
+ * shared too. `end()` is a no-op: the instance lifecycle is owned by whoever
+ * created it (see `registerPglite`), not by an individual client.
+ */
+export declare const createPgliteClient: (db: PGlite) => QueryablePgClient;

package/client.js

@@ -0,0 +1,23 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.createPgliteClient = void 0;
+const runner_1 = require("./runner");
+/**
+ * Build a `pg.Client`-shaped object backed by an existing PGlite instance.
+ *
+ * Every client returned for the same instance shares that single in-process
+ * session, so transaction control (`BEGIN`/`SAVEPOINT`/`ROLLBACK`/`COMMIT`) is
+ * shared too. `end()` is a no-op: the instance lifecycle is owned by whoever
+ * created it (see `registerPglite`), not by an individual client.
+ */
+const createPgliteClient = (db) => {
+    const query = (0, runner_1.boundQuery)(db);
+    return {
+        connect: async () => {
+            await db.waitReady;
+        },
+        query,
+        end: async () => { }
+    };
+};
+exports.createPgliteClient = createPgliteClient;

package/esm/client.js

@@ -0,0 +1,19 @@
+import { boundQuery } from './runner';
+/**
+ * Build a `pg.Client`-shaped object backed by an existing PGlite instance.
+ *
+ * Every client returned for the same instance shares that single in-process
+ * session, so transaction control (`BEGIN`/`SAVEPOINT`/`ROLLBACK`/`COMMIT`) is
+ * shared too. `end()` is a no-op: the instance lifecycle is owned by whoever
+ * created it (see `registerPglite`), not by an individual client.
+ */
+export const createPgliteClient = (db) => {
+    const query = boundQuery(db);
+    return {
+        connect: async () => {
+            await db.waitReady;
+        },
+        query,
+        end: async () => { }
+    };
+};

package/esm/index.js

@@ -0,0 +1,35 @@
+import { PGlite } from '@electric-sql/pglite';
+import { getActivePgPoolFactory, registerPgPoolFactory } from 'pg-cache';
+import { createPglitePool } from './pool';
+export { createPgliteClient } from './client';
+export { createPglitePool } from './pool';
+/**
+ * Create (or adopt) a PGlite instance and register it as the pg-cache pool
+ * factory, so every `getPgPool()` call — and therefore the unmodified pgpm
+ * engine — talks to PGlite in-process. No socket, no Postgres server.
+ *
+ * @example
+ * const { db, close } = await registerPglite();
+ * const migrate = new PgpmMigrate({ database: 'postgres', ... });
+ * await migrate.deploy({ modulePath });
+ * await close();
+ */
+export const registerPglite = async (options = {}) => {
+    const db = options.instance ??
+        (await PGlite.create({ dataDir: options.dataDir, extensions: options.extensions }));
+    await db.waitReady;
+    for (const sql of options.extensionSql ?? []) {
+        await db.exec(sql);
+    }
+    const previous = getActivePgPoolFactory();
+    const pool = createPglitePool(db);
+    registerPgPoolFactory(() => pool);
+    return {
+        db,
+        unregister: () => registerPgPoolFactory(previous),
+        close: async () => {
+            registerPgPoolFactory(previous);
+            await db.close();
+        }
+    };
+};

package/esm/pool.js

@@ -0,0 +1,34 @@
+import { boundQuery } from './runner';
+/**
+ * Build a `QueryablePool` backed by an existing PGlite instance.
+ *
+ * PGlite is a single in-process engine (one session), so both `pool.query` and
+ * the client returned by `connect()` funnel to the same instance. That is
+ * exactly what lets pgpm's transactional deploy work: the `BEGIN` opened on the
+ * connected client and the `isDeployed()` check issued via `pool.query` share
+ * one session, so there is no cross-connection deadlock (the failure mode of a
+ * multi-connection pool against a single-connection backend).
+ *
+ * `end()` intentionally does NOT close the PGlite instance: the same instance
+ * may back several cached pool wrappers (pg-cache keys by database name), and
+ * its lifecycle is owned by whoever created it (see `registerPglite`).
+ */
+export const createPglitePool = (db) => {
+    let ended = false;
+    const query = boundQuery(db);
+    const client = {
+        query,
+        release: () => { }
+    };
+    const pool = {
+        get ended() {
+            return ended;
+        },
+        query,
+        connect: async () => client,
+        end: async () => {
+            ended = true;
+        }
+    };
+    return pool;
+};

package/esm/runner.js

@@ -0,0 +1,33 @@
+const toResult = (r) => {
+    const rows = r?.rows ?? [];
+    const rowCount = typeof r?.affectedRows === 'number' ? r.affectedRows : rows.length;
+    return { rows, rowCount, fields: r?.fields ?? [] };
+};
+/**
+ * Run a statement against the single in-process PGlite engine.
+ *
+ * PGlite mirrors node-`pg`'s two protocols:
+ * - parameterized (`$1`, ...) -> `db.query` (extended protocol, single statement)
+ * - no parameters -> `db.exec` (simple protocol, supports the multi-statement
+ *   bootstrap SQL pgpm runs in `initialize()`), returning the last result.
+ */
+export const run = async (db, text, values) => {
+    if (values && values.length > 0) {
+        return toResult(await db.query(text, values));
+    }
+    const results = await db.exec(text);
+    const last = Array.isArray(results) && results.length ? results[results.length - 1] : undefined;
+    return toResult(last);
+};
+/** Normalize the two call shapes pg accepts: `(text, values)` or `({ text, values })`. */
+export const normalize = (first, second) => {
+    if (first && typeof first === 'object' && 'text' in first) {
+        return { text: first.text, values: first.values };
+    }
+    return { text: first, values: second };
+};
+/** A bound `(text, values | { text, values })` query function over a PGlite instance. */
+export const boundQuery = (db) => (text, values) => {
+    const q = normalize(text, values);
+    return run(db, q.text, q.values);
+};

package/index.d.ts

@@ -0,0 +1,43 @@
+import { PGlite } from '@electric-sql/pglite';
+export { createPgliteClient, type QueryablePgClient } from './client';
+export { createPglitePool } from './pool';
+export type { PgResultLike } from './runner';
+export interface PgliteAdapterOptions {
+    /** Persist to a directory (default: in-memory). */
+    dataDir?: string;
+    /**
+     * PGlite WASM extensions to register at construction, e.g. `{ vector }` from
+     * `@electric-sql/pglite-pgvector`. The corresponding `CREATE EXTENSION`
+     * statements still run out-of-band (see `extensionSql`) because pgpm's
+     * `cleanSql` strips `CREATE EXTENSION` from migration scripts.
+     */
+    extensions?: Record<string, any>;
+    /**
+     * SQL run once after the instance is ready — the place for
+     * `CREATE EXTENSION IF NOT EXISTS ...`, mirroring pgsql-test's
+     * `DbAdmin.installExtensions()`.
+     */
+    extensionSql?: string[];
+    /** Reuse an already-created PGlite instance instead of creating one. */
+    instance?: PGlite;
+}
+export interface PgliteAdapterHandle {
+    /** The underlying PGlite instance (for direct queries / lifecycle control). */
+    db: PGlite;
+    /** Restore the previously-active pg-cache factory. Does not close `db`. */
+    unregister: () => void;
+    /** Unregister and close the PGlite instance. */
+    close: () => Promise<void>;
+}
+/**
+ * Create (or adopt) a PGlite instance and register it as the pg-cache pool
+ * factory, so every `getPgPool()` call — and therefore the unmodified pgpm
+ * engine — talks to PGlite in-process. No socket, no Postgres server.
+ *
+ * @example
+ * const { db, close } = await registerPglite();
+ * const migrate = new PgpmMigrate({ database: 'postgres', ... });
+ * await migrate.deploy({ modulePath });
+ * await close();
+ */
+export declare const registerPglite: (options?: PgliteAdapterOptions) => Promise<PgliteAdapterHandle>;

package/index.js

@@ -0,0 +1,41 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.registerPglite = exports.createPglitePool = exports.createPgliteClient = void 0;
+const pglite_1 = require("@electric-sql/pglite");
+const pg_cache_1 = require("pg-cache");
+const pool_1 = require("./pool");
+var client_1 = require("./client");
+Object.defineProperty(exports, "createPgliteClient", { enumerable: true, get: function () { return client_1.createPgliteClient; } });
+var pool_2 = require("./pool");
+Object.defineProperty(exports, "createPglitePool", { enumerable: true, get: function () { return pool_2.createPglitePool; } });
+/**
+ * Create (or adopt) a PGlite instance and register it as the pg-cache pool
+ * factory, so every `getPgPool()` call — and therefore the unmodified pgpm
+ * engine — talks to PGlite in-process. No socket, no Postgres server.
+ *
+ * @example
+ * const { db, close } = await registerPglite();
+ * const migrate = new PgpmMigrate({ database: 'postgres', ... });
+ * await migrate.deploy({ modulePath });
+ * await close();
+ */
+const registerPglite = async (options = {}) => {
+    const db = options.instance ??
+        (await pglite_1.PGlite.create({ dataDir: options.dataDir, extensions: options.extensions }));
+    await db.waitReady;
+    for (const sql of options.extensionSql ?? []) {
+        await db.exec(sql);
+    }
+    const previous = (0, pg_cache_1.getActivePgPoolFactory)();
+    const pool = (0, pool_1.createPglitePool)(db);
+    (0, pg_cache_1.registerPgPoolFactory)(() => pool);
+    return {
+        db,
+        unregister: () => (0, pg_cache_1.registerPgPoolFactory)(previous),
+        close: async () => {
+            (0, pg_cache_1.registerPgPoolFactory)(previous);
+            await db.close();
+        }
+    };
+};
+exports.registerPglite = registerPglite;

package/package.json

@@ -0,0 +1,55 @@
+{
+  "name": "@pgpmjs/pglite-adapter",
+  "version": "0.1.0",
+  "author": "Constructive <developers@constructive.io>",
+  "description": "PGlite driver for pgpm — registers an in-process PGlite instance as the pg-cache pool factory so the unmodified pgpm engine deploys into PGlite (WASM Postgres) with no server",
+  "main": "index.js",
+  "module": "esm/index.js",
+  "types": "index.d.ts",
+  "homepage": "https://github.com/constructive-io/constructive",
+  "license": "MIT",
+  "publishConfig": {
+    "access": "public",
+    "directory": "dist"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/constructive-io/constructive"
+  },
+  "bugs": {
+    "url": "https://github.com/constructive-io/constructive/issues"
+  },
+  "keywords": [
+    "postgres",
+    "postgresql",
+    "pglite",
+    "wasm",
+    "pgpm",
+    "migrations",
+    "pg-cache",
+    "adapter",
+    "driver"
+  ],
+  "scripts": {
+    "clean": "makage clean",
+    "prepack": "npm run build",
+    "build": "makage build",
+    "build:dev": "makage build --dev",
+    "lint": "eslint . --fix",
+    "test": "NODE_OPTIONS=--experimental-vm-modules jest --passWithNoTests",
+    "test:watch": "NODE_OPTIONS=--experimental-vm-modules jest --watch"
+  },
+  "devDependencies": {
+    "@electric-sql/pglite": "0.5.4",
+    "@pgpmjs/core": "^6.27.1",
+    "@types/pg": "^8.20.0",
+    "makage": "^0.3.0"
+  },
+  "dependencies": {
+    "pg-cache": "^3.14.0"
+  },
+  "peerDependencies": {
+    "@electric-sql/pglite": ">=0.5.0"
+  },
+  "gitHead": "7cbe15fac21a9345b169203ba9542ba9a50c866c"
+}

package/pool.d.ts

@@ -0,0 +1,17 @@
+import type { PGlite } from '@electric-sql/pglite';
+import type { QueryablePool } from 'pg-cache';
+/**
+ * Build a `QueryablePool` backed by an existing PGlite instance.
+ *
+ * PGlite is a single in-process engine (one session), so both `pool.query` and
+ * the client returned by `connect()` funnel to the same instance. That is
+ * exactly what lets pgpm's transactional deploy work: the `BEGIN` opened on the
+ * connected client and the `isDeployed()` check issued via `pool.query` share
+ * one session, so there is no cross-connection deadlock (the failure mode of a
+ * multi-connection pool against a single-connection backend).
+ *
+ * `end()` intentionally does NOT close the PGlite instance: the same instance
+ * may back several cached pool wrappers (pg-cache keys by database name), and
+ * its lifecycle is owned by whoever created it (see `registerPglite`).
+ */
+export declare const createPglitePool: (db: PGlite) => QueryablePool;

package/pool.js

@@ -0,0 +1,38 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.createPglitePool = void 0;
+const runner_1 = require("./runner");
+/**
+ * Build a `QueryablePool` backed by an existing PGlite instance.
+ *
+ * PGlite is a single in-process engine (one session), so both `pool.query` and
+ * the client returned by `connect()` funnel to the same instance. That is
+ * exactly what lets pgpm's transactional deploy work: the `BEGIN` opened on the
+ * connected client and the `isDeployed()` check issued via `pool.query` share
+ * one session, so there is no cross-connection deadlock (the failure mode of a
+ * multi-connection pool against a single-connection backend).
+ *
+ * `end()` intentionally does NOT close the PGlite instance: the same instance
+ * may back several cached pool wrappers (pg-cache keys by database name), and
+ * its lifecycle is owned by whoever created it (see `registerPglite`).
+ */
+const createPglitePool = (db) => {
+    let ended = false;
+    const query = (0, runner_1.boundQuery)(db);
+    const client = {
+        query,
+        release: () => { }
+    };
+    const pool = {
+        get ended() {
+            return ended;
+        },
+        query,
+        connect: async () => client,
+        end: async () => {
+            ended = true;
+        }
+    };
+    return pool;
+};
+exports.createPglitePool = createPglitePool;

package/runner.d.ts

@@ -0,0 +1,27 @@
+import type { PGlite } from '@electric-sql/pglite';
+/**
+ * A node-`pg`-shaped result. pgpm / pgsql-client read `rows` and (occasionally)
+ * `rowCount`, so we normalize PGlite's `{ rows, affectedRows, fields }` onto that
+ * shape.
+ */
+export interface PgResultLike {
+    rows: any[];
+    rowCount: number;
+    fields: any[];
+}
+/**
+ * Run a statement against the single in-process PGlite engine.
+ *
+ * PGlite mirrors node-`pg`'s two protocols:
+ * - parameterized (`$1`, ...) -> `db.query` (extended protocol, single statement)
+ * - no parameters -> `db.exec` (simple protocol, supports the multi-statement
+ *   bootstrap SQL pgpm runs in `initialize()`), returning the last result.
+ */
+export declare const run: (db: PGlite, text: string, values?: any[]) => Promise<PgResultLike>;
+/** Normalize the two call shapes pg accepts: `(text, values)` or `({ text, values })`. */
+export declare const normalize: (first: any, second?: any[]) => {
+    text: string;
+    values?: any[];
+};
+/** A bound `(text, values | { text, values })` query function over a PGlite instance. */
+export declare const boundQuery: (db: PGlite) => (text: any, values?: any[]) => Promise<PgResultLike>;

package/runner.js

@@ -0,0 +1,39 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.boundQuery = exports.normalize = exports.run = void 0;
+const toResult = (r) => {
+    const rows = r?.rows ?? [];
+    const rowCount = typeof r?.affectedRows === 'number' ? r.affectedRows : rows.length;
+    return { rows, rowCount, fields: r?.fields ?? [] };
+};
+/**
+ * Run a statement against the single in-process PGlite engine.
+ *
+ * PGlite mirrors node-`pg`'s two protocols:
+ * - parameterized (`$1`, ...) -> `db.query` (extended protocol, single statement)
+ * - no parameters -> `db.exec` (simple protocol, supports the multi-statement
+ *   bootstrap SQL pgpm runs in `initialize()`), returning the last result.
+ */
+const run = async (db, text, values) => {
+    if (values && values.length > 0) {
+        return toResult(await db.query(text, values));
+    }
+    const results = await db.exec(text);
+    const last = Array.isArray(results) && results.length ? results[results.length - 1] : undefined;
+    return toResult(last);
+};
+exports.run = run;
+/** Normalize the two call shapes pg accepts: `(text, values)` or `({ text, values })`. */
+const normalize = (first, second) => {
+    if (first && typeof first === 'object' && 'text' in first) {
+        return { text: first.text, values: first.values };
+    }
+    return { text: first, values: second };
+};
+exports.normalize = normalize;
+/** A bound `(text, values | { text, values })` query function over a PGlite instance. */
+const boundQuery = (db) => (text, values) => {
+    const q = (0, exports.normalize)(text, values);
+    return (0, exports.run)(db, q.text, q.values);
+};
+exports.boundQuery = boundQuery;