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

@adliihjs/graphql-postgres-subscriptions

v3.0.0

Published

PostgreSQL-backed PubSub implementation for GraphQL subscriptions (graphql-subscriptions v3)

Readme

@adliihjs/graphql-postgres-subscriptions

A graphql subscriptions implementation using postgres and apollo's graphql-subscriptions.

This package implements the PubSubEngine Interface from the graphql-subscriptions package and also the new AsyncIterator interface. It allows you to connect your subscriptions manger to a postgres based Pub Sub mechanism to support multiple subscription manager instances.

Installation

The scoped name is not on the public npm registry yet. Install from GitHub (the prepare script runs tsc so dist/ exists after install):

npm install github:adliih/graphql-postgres-subscriptions

Pin a branch, tag, or commit:

npm install github:adliih/graphql-postgres-subscriptions#main
npm install github:adliih/graphql-postgres-subscriptions#v3.0.0

Yarn / pnpm equivalents: yarn add github:adliih/graphql-postgres-subscriptions or pnpm add github:adliih/graphql-postgres-subscriptions.

Note: Installing from git relies on this package’s devDependencies (e.g. TypeScript) for the build. Avoid root installs with npm install --omit=dev (or production-only CI) unless you vendor a prebuilt copy (e.g. npm pack tarball from a release).

Other ways to distribute

  • GitHub Packages (npm) — publish to https://npm.pkg.github.com with a GITHUB_TOKEN / PAT; consumers set .npmrc for the scope. No npmjs.com account required beyond GitHub access to the package.
  • Release assets — run npm pack, attach the .tgz to a GitHub Release; consumers run npm install ./graphql-postgres-subscriptions-3.0.0.tgz.
  • Commit dist/ — if you need minimal install size and no compile step, stop ignoring dist/ and commit built output (tradeoff: noisier diffs).

Usage

Example app: https://github.com/GraphQLCollege/apollo-subscriptions-example

First of all, follow the instructions in graphql-subscriptions to add subscriptions to your app.

Afterwards replace PubSub with PostgresPubSub:

// Before
import { PubSub } from "graphql-subscriptions";

export const pubsub = new PubSub();
// After
import { PostgresPubSub } from "@adliihjs/graphql-postgres-subscriptions";

export const pubsub = new PostgresPubSub();

This library uses node-postgres to connect to PostgreSQL. If you want to customize connection options, please refer to their connection docs.

You have three options:

If you don's send any argument to new PostgresPubSub(), we'll create a postgres client with no arguments.

You can also pass node-postgres connection options to PostgresPubSub.

You can instantiate your own client and pass it to PostgresPubSub. Like this:

import { PostgresPubSub } from "@adliihjs/graphql-postgres-subscriptions";
import { Client } from "pg";

const client = new Client();
await client.connect();
const pubsub = new PostgresPubSub({ client });

Important: Don't pass clients from pg's Pool to PostgresPubSub. As node-postgres creator states in this StackOverflow answer, the client needs to be around and not shared so pg can properly handle NOTIFY messages (which this library uses under the hood)

commonMessageHandler

The second argument to new PostgresPubSub() is the commonMessageHandler. The common message handler gets called with the received message from PostgreSQL. You can transform the message before it is passed to the individual filter/resolver methods of the subscribers. This way it is for example possible to inject one instance of a DataLoader which can be used in all filter/resolver methods.

const getDataLoader = () => new DataLoader(...)
const commonMessageHandler = ({attributes: {id}, data}) => ({id, dataLoader: getDataLoader()})
const pubsub = new PostgresPubSub({ client, commonMessageHandler });
export const resolvers = {
  Subscription: {
    somethingChanged: {
      resolve: ({ id, dataLoader }) => dataLoader.load(id)
    }
  }
};

Error handling

PostgresPubSub instances emit a special event called "error". This event's payload is an instance of Javascript's Error. You can get the error's text using error.message.

const ps = new PostgresPubSub({ client });

ps.subscribe("error", err => {
  console.log(err.message); // -> "payload string too long"
}).then(() => ps.publish("a", "a".repeat(9000)));

For example you can log all error messages (including stack traces and friends) using something like this:

ps.subscribe("error", console.error);

Development

This project has an integration test suite that uses jest to make sure everything works correctly.

We use Docker to spin up a PostgreSQL instance before running the tests. To run them, type the following commands:

  • docker-compose build
  • docker-compose run test