import { PGlite } from '@electric-sql/pglite';
import type { PgpmDriverSession } from '@pgpmjs/types';
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>;
/**
 * The pgpm driver-plugin entrypoint (`createPgpmDriver`), which is how the pgpm
 * CLI activates this backend for `--engine pglite` / `--driver
 * @pgpmjs/pglite-adapter`. It registers the in-process PGlite instance as the
 * pool factory — exactly what {@link registerPglite} does — and describes what
 * PGlite cannot do so the CLI skips server-only steps generically.
 *
 * PGlite is one WASM instance with a single superuser session, so: the instance
 * *is* the database (no `createdb`), there is no `pg_dump` binary and no server
 * to manage, and a second concurrent connection is not available.
 */
export declare const createPgpmDriver: (options?: PgliteAdapterOptions) => Promise<PgpmDriverSession>;