Knex.js PGlite Dialect

A dialect for using PGlite with Knex.js.

Table of Contents

• Language
• Installation
• Usage
  • Easy initialization
  • Injecting a PGlite instance
• API
  • client
  • connection
    • pglite
• License

Language

• English
• 한국어

Installation

Install with the following commands.

# using npm
npm i knex @electric-sql/pglite @harryplusplus/knex-pglite
# using pnpm
pnpm add knex @electric-sql/pglite @harryplusplus/knex-pglite

Warning

Yarn and Bun environments have not been tested yet for compatibility.

Usage

Easy initialization

Configure the client and connection properties of the Knex creation function. The value of the connection property is used as the dataDir parameter of the PGlite constructor.

Note

For detailed specifications of dataDir in the PGlite constructor, please refer to the PGlite API dataDir documentation.

The example below shows how to do an easy initialization.

import { PGliteDialect } from "@harryplusplus/knex-pglite";
import Knex from "knex";

const knex = Knex({
  client: PGliteDialect, // Knex PGlite Dialect

  // In-memory ephemeral storage
  connection: {},
  connection: "",
  connection: "memory://",

  // IndexedDB storage
  connection: "idb://",

  // File system storage
  connection: "/my/pglite/data",
});

Warning

Without the connection property, Knex operates in unconnected mode. Since the unconnected mode works as a SQL string generator, you must define a value, even if it is an empty object, in order to use PGlite.

Warning

connection values ​​in the form of a File URI (e.g. file:///my/pglite/data) cannot be used because they are not parsed in a form suitable for initializing PGlite according to the current Knex connection string parsing rules. Please enter the file path (e.g. /my/pglite/data) rather than the file URI.

Injecting a PGlite instance

When using the Easy initialization method, the PGlite instance becomes owned by the Knex instance. In other words, a PGlite instance shares its lifecycle with a Knex instance.

For a PGlite instance with in-memory temporary storage, sharing the lifecycle with a Knex instance may not meet your needs depending on your use case. Additionally, various parameters for PGlite initialization cannot be utilized.

Configure the connection.pglite property to a synchronous or asynchronous function that returns a PGlite instance. In this case, Knex internally considers the PGlite instance to be in a borrowed state. In other words, Knex does not manage the creation and destruction of PGlite instances, since it delegates the lifecycle of PGlite instances to an external entity.

The example below shows how to inject a PGlite instance.

import { PGlite } from "@electric-sql/pglite";
import Knex from "knex";
import {
  PGliteConnectionConfig,
  PGliteDialect,
} from "@harryplusplus/knex-pglite";

const pglite = new PGlite();

const knex = Knex({
  client: PGliteDialect,
  connection: {
    pglite: () => pglite,
  } satisfies PGliteConnectionConfig as Knex.Knex.StaticConnectionConfig,
});

Note

Here's why we use satisfies PGliteConnectionConfig as Knex.Knex.StaticConnectionConfig:

1. Use satisfies PGliteConnectionConfig to enforce the type of the connection property required by the Knex PGlite Dialect.
2. Assert that it conforms to the Knex type definition using as Knex.Knex.StaticConnectionConfig.

API

Configure the following properties from the parameters of the Knex creation function:

client

To use the Knex PGlite Dialect, you must specify the PGliteDialect class in the client property.

connection

The type of the connection property is:

export interface PGliteConnectionConfig {
  pglite?: PGliteProvider;
}

The following are the properties for configuring connection.

pglite

The type of the pglite attribute is:

export interface PGliteProvider {
  (): MaybePromise<PGlite>; // (): PGlite | Promise<PGlite>
}

Note

To learn more about PGlite's various features, please read the PGlite API documentation.

License

MIT