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

@stackline/types-pg

v1.0.3

Published

Dependency-reviewed TypeScript definitions compatible with @types/pg 8.23.1

Readme

@stackline/types-pg

Dependency-reviewed TypeScript definitions compatible with @types/pg 8.23.1.

npm version license GitHub repository Docs Reddit community

Documentation | npm | Issues | Repository

Current package version: 1.0.3


Why this package?

Dependency-reviewed TypeScript definitions compatible with @types/[email protected].

The declaration files are unchanged from DefinitelyTyped. This fork replaces the historical [email protected] -> postgres-interval -> xtend dependency branch with @stackline/pg-types, pins the remaining type dependencies, and verifies the packed package in clean TypeScript consumers.

Compatibility

| Item | Value | | --- | --- | | Package | @stackline/[email protected] | | Node.js runtime | >=16 | | CommonJS / primary entry | ./index.js | | Type declarations | index.d.ts |

  • Declaration baseline: @types/[email protected].
  • Runtime baseline: [email protected] and @stackline/[email protected].
  • TypeScript: 5.6 and newer, matching the source package metadata.
  • CJS and ESM declaration entry points are preserved.
  • Deep pg/lib/* type imports are preserved through the alias installation.

See DEPENDENCY_REVIEW.md, COMPATIBILITY.md, and SECURITY.md.

Installation

Install

Use the historical @types/pg location so TypeScript discovery and existing imports remain unchanged:

npm install pg@npm:@stackline/pg @types/pg@npm:@stackline/types-pg

Usage

Existing source continues to work:

import { Pool, type PoolConfig, type QueryResultRow } from "pg";

const config: PoolConfig = {
  connectionString: process.env.DATABASE_URL,
  max: 10,
};

interface UserRow extends QueryResultRow {
  id: number;
  name: string;
}

const pool = new Pool(config);
const result = await pool.query<UserRow>("select id, name from users");

The scoped package can also be imported explicitly for types:

npm install @stackline/types-pg
import type { PoolConfig } from "@stackline/types-pg";

Security

Review inputs and the package-specific compatibility limits before processing untrusted data. Report suspected vulnerabilities as described in the security policy.

Local Development

git clone https://github.com/alexandroit/stackline-types-pg.git
cd stackline-types-pg
npm ci
npm run verify

Release tooling uses Node.js 24.20.0 and npm 11.19.0. The consumer runtime contract remains the one documented above.

Consumer Smoke Test

Run the repository's existing consumer/package check after installing development dependencies:

npm run test:smoke

Release Checklist

Run npm run verify and inspect the package contents before release. Publish a new version through the GitHub Actions publishing workflow, using the SHA-512 digest of the reviewed tarball. Verify the exact published version, tarball integrity, and npm provenance after the run.

License

MIT. The DefinitelyTyped license and author credit are preserved in LICENSE, NOTICE, and UPSTREAM_README.md.

Credits and original authors

Original copyright, license notices and contributor acknowledgements remain part of this distribution. Stackline maintenance does not replace authorship of the original work.

Community and Links

Use this repository's issue tracker for reproducible bugs and feature requests. Join r/Stackline for examples, usage questions and release discussions.