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

@form-engine-ts/storage-postgres

v8.2.0

Published

Readme

@form-engine-ts/storage-postgres

PostgreSQL implementation of the complete form-engine-ts storage contract using an injected node-postgres-compatible query client.

Install

pnpm add @form-engine-ts/core @form-engine-ts/storage-postgres pg

Quick start

import { Pool } from "pg";
import { createPostgresStorage } from "@form-engine-ts/storage-postgres";

const pool = new Pool({ connectionString: process.env.DATABASE_URL });
const storage = createPostgresStorage({ client: pool, autoMigrate: true });

await storage.saveSchema(schema);
await storage.saveSubmission(submission);
const submissions = await storage.listSubmissions(schema.id, schema.version, {
  since: "2026-01-01T00:00:00.000Z",
  until: "2026-01-31T23:59:59.999Z"
});

client may be a Pool, Client, or a wrapper exposing the same query(text, values) shape. The caller owns connections and transactions. autoMigrate defaults to false; when enabled, the adapter lazily runs idempotent CREATE TABLE/INDEX IF NOT EXISTS statements once before its first operation. Use a migration framework for production schema evolution.

Schemas use a (form_id, form_version) primary key and JSONB payload. Responses use their globally unique ID as the primary key, retain searchable form/version/locale/timestamp columns, and store the complete submission as JSONB. Custom table names must be safe SQL identifiers. Range boundaries are inclusive and results are ordered by submission time and then ID. Schema deletion never cascades to responses; clearResponses(formId) removes every version of one form, while clear() deletes rows only from the configured tables.

listSubmissionPage(formId, { version, pageSize, cursor, since, until, locale }) uses a parameterized keyset query over submitted_at, response_id. Its opaque cursor handles equal timestamps without OFFSET gaps or duplicates. metadataFilters and custom filter predicates are applied before page sizing.

saveSubmissionWithinLimit(submission, maxResponses, options?) requires the injected client's transaction method. It uses a transaction-scoped advisory lock per form version by default; responseLimitScope: "form" locks and counts all versions together before inserting the response.