npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

pglite-pool

v0.0.2

Published

Simplifies using [`pglite`](https://github.com/electric-sql/pglite) in Node/Bun for codegen and tests by using [`pglite-server`](https://www.npmjs.com/package/pglite-server) to create a Postgres server at a random port.

Downloads

18

Readme

pglite-pool

Simplifies using pglite in Node/Bun for codegen and tests by using pglite-server to create a Postgres server at a random port.

Each instance created by getPostgres / withPostgres is fully ephemeral and isolated.

Usage

Both a teardown style and a callback style are supported.

Teardown style

import { getPostgres } from 'pglite-pool';

async function main() {
  const pg = await getPostgres()

  // pg.pool is an already connected Postgres pool
  const pool = pg.pool

  // Do pool things...
  await pool.query('select 1')

  const client = await pool.connect()
  await client.query('select 1')
  client.release()

  // Teardowns the pool, server, and in-memory Postgres instance
  await pg.teardown()
}

Callback Style

import { withPostgres } from 'pglite-pool';

async function main() {
  const anythingString = await withPostgres(async (pg) => {
    const pool = pg.pool
    await pool.query('select 1')
    return 'anything';
    // Teardown happens automatically after return
  })
}

With Connection String

In both the callback and teardown styles, the pg objection has a connectionString property.

This is useful for plugging into libraries such as kanel or graphile-migrate which construct their own Pool object internally.

For example, to run Kanel codegen without Docker or external setup, do:

// codegen.ts
import { processDatabase } from "kanel";
import { makeKyselyHook } from "kanel-kysely";
import { withPostgres } from 'pglite-pool'

const makeConfig = (connectionString: string) => {
  schemas: ["my_schema"],
  outputPath: "./src/database",
  preRenderHooks: [makeKyselyHook()],
  connection: {
    connectionString,
  },
};

await withPostgres(async (pg) => {
  await processDatabase(makeConfig(pg.connectionString));
})

run();

And then bun run codegen.ts just works™.

A full graphile-migrate + Kanel example might be:

import { processDatabase } from "kanel";
import { makeKyselyHook } from "kanel-kysely";
import { withPostgres } from 'pglite-pool'
import { watch } from "graphile-migrate";

const makeConfig = (connectionString: string) => {
  schemas: ["my_schema"],
  outputPath: "./src/database",
  preRenderHooks: [makeKyselyHook()],
  connection: {
    connectionString,
  },
};

await withPostgres(async (pg) => {
  await watch(
    {
      connectionString: pg.connectionString,
      migrationsFolder: "./migrations", // or other path to migrations folder
    },
    true
  );

  await processDatabase(makeConfig(pg.connectionString));
})

run();