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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@oliphaunt/wasix-tools

v0.2.4

Published

Optional in-process PostgreSQL pg_dump and psql runners for Oliphaunt WASIX.

Readme

@oliphaunt/wasix-tools

Optional standard PostgreSQL pg_dump and non-interactive psql runners for an open @oliphaunt/wasix-ts database. This package remains the public opt-in facade on every host. Browsers load separately carried portable tool binaries; Node.js, Bun, Deno, and Electron call the copies compiled into the matching Node-API platform carrier.

pgDump() returns PostgreSQL's ordinary plain SQL dump, including normal COPY data. psql() accepts a command or script and can restore that output. Both operations exclusively own the database session until they finish. They reset PostgreSQL session state before and after running, so raw-protocol callers must not expect prepared statements or session settings to survive.

bun add @oliphaunt/wasix-ts @oliphaunt/wasix-tools
import Oliphaunt from '@oliphaunt/wasix-ts';
import WorkerOliphaunt from '@oliphaunt/wasix-ts/worker';
import { pgDump, psql } from '@oliphaunt/wasix-tools';

await using source = await Oliphaunt.open();
const sql = await pgDump(source, { args: ['--schema-only'] });
await using target = await WorkerOliphaunt.open();
await psql(target, { script: sql });

pgDump() supports databases from the root, /direct, and /worker entrypoints. In browsers, psql() requires /worker because COPY restore is full duplex. On Node.js, Bun, Deno, and Electron the Rust tool bridge supports psql() on all three entrypoints. Ordinary PostgreSQL arguments are passed through, except connection, input/output, encoding, dump format, compression, and parallel-job arguments owned by the runner. pgDump() always uses plain UTF-8 output and rejects custom formats; it does not force --inserts or rewrite valid dump SQL. psql() accepts command or script, uses no user psqlrc, and stops on the first SQL error. Interactive input and pg_restore are not part of this package.

Tool failures throw PostgresToolError with tool, exitCode, stdout, and stderr fields.

Maintainer commands

After installing the pinned workspace tools and dependencies, run these from this directory:

moon run oliphaunt-wasix-tools-ts:build
moon run oliphaunt-wasix-tools-ts:typecheck
moon run oliphaunt-wasix-tools-ts:test
moon run oliphaunt-wasix-tools-ts:package

Build and typecheck first build the SDK's actual declarations; they do not compile PostgreSQL, Wasmer or the Node addon. Packaging depends on this build and stages only the facade. bun run build and bun run typecheck consume an already built SDK. The separate postgres-tools-wasix:test-consumer and postgres-tools-wasix:test-browser tasks produce the runtime/tool dependencies and exercise the installed packages on their respective hosts.