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

@pg-boss/proxy

v0.4.0

Published

HTTP proxy for pg-boss

Readme

@pg-boss/proxy

A HTTP proxy for pg-boss methods, to support use cases such as platform compatibility and connection pooling or scalability.

All background processing is disabled by default (the opposite of how pg-boss normally works). A pg-boss instance is started via start(), which opens the database connection.

Quick Start

As a library (import into your own Node app):

import { createProxyServerNode } from '@pg-boss/proxy/node'

const proxy = await createProxyServerNode()
await proxy.start()
// Reads DATABASE_URL from process.env, listens on PORT (default 3000)

From source (clone the repo and run the built-in dev server):

npm run dev

Then visit:

  • http://localhost:3000 - Proxy home page with links to all endpoints
  • http://localhost:3000/docs - Interactive Swagger documentation
  • http://localhost:3000/openapi.json - OpenAPI spec

API Usage Examples

Once the proxy is running, you can interact with it using any HTTP client:

# Send a job to a queue
curl -X POST http://localhost:3000/api/send \
  -H "Content-Type: application/json" \
  -d '{"name": "my-queue", "data": {"key": "value"}}'

# Fetch jobs from a queue
curl -X POST http://localhost:3000/api/fetch \
  -H "Content-Type: application/json" \
  -d '{"name": "my-queue"}'

# Get queue information
curl "http://localhost:3000/api/getQueue?name=my-queue"

# Get all queues
curl "http://localhost:3000/api/getQueues"

Response Format

All endpoints return a consistent JSON envelope:

// Success
{ "ok": true, "result": <value | null> }

// Error
{ "ok": false, "error": { "message": "..." } }

The result field contains the direct return value of the underlying pg-boss method. HTTP status codes used: 200 for success, 400 for invalid input, 413 for body too large, and 500 for server errors.

Entry Points

This package ships a runtime-neutral entry point and a Node-only entry point.

Runtime-neutral (default)

Use this when you want a runtime-neutral entry point:

import { createProxyService } from '@pg-boss/proxy'

const { app, start, stop } = await createProxyService({
  options: {
    connectionString: 'postgres://user:pass@host/database'
  }
})

await start()
// later
await stop()

Node Convenience Entry Point

If you want a ready-to-listen Node server with automatic shutdown signal wiring:

import { createProxyServerNode } from '@pg-boss/proxy/node'

const proxy = await createProxyServerNode()
await proxy.start()

Lifecycle Wiring by Runtime

createProxyServerNode automatically attaches SIGINT and SIGTERM handlers. Set attachSignals: false to opt out and manage shutdown yourself.

For createProxyService (runtime-neutral), or for non-Node runtimes, wire shutdown manually using attachShutdownListeners and the appropriate adapter:

Node

import { attachShutdownListeners, createProxyService, nodeShutdownAdapter } from '@pg-boss/proxy'

const { app, start, stop } = await createProxyService({
  options: { connectionString: process.env.DATABASE_URL }
})

await start()

attachShutdownListeners(['SIGINT', 'SIGTERM'], nodeShutdownAdapter, stop)

Deno

import { attachShutdownListeners, createDenoShutdownAdapter, createProxyService } from '@pg-boss/proxy'

const { start, stop } = await createProxyService({
  options: {
    connectionString: Deno.env.get('DATABASE_URL')
  }
})

await start()

attachShutdownListeners(['SIGINT', 'SIGTERM'], createDenoShutdownAdapter(), stop)

Bun

import { attachShutdownListeners, createProxyService, bunShutdownAdapter } from '@pg-boss/proxy'

const { start, stop } = await createProxyService({
  options: { connectionString: process.env.DATABASE_URL }
})

await start()

attachShutdownListeners(['SIGINT', 'SIGTERM'], bunShutdownAdapter, stop)

Configuration

You can configure the proxy using either code options or environment variables. Code options take precedence over environment variables if both are set.

Code Options

The proxy accepts the following options:

import { createProxyService } from '@pg-boss/proxy'

const { app, boss } = await createProxyService({
  options: { connectionString: process.env.DATABASE_URL },
  prefix: '/api',
  requestLogger: true,
  logFormat: 'text', // 'text' or 'json'
  exposeErrors: false,
  bodyLimit: 1024 * 1024,
  routes: {
    allow: ['send', 'fetch'],
    deny: ['deleteQueue']
  },
  pages: {
    root: true,
    docs: true,
    openapi: true
  },
  auth: {
    username: 'admin',
    password: 'secret'
  },
  cors: {
    origin: 'https://example.com',
    methods: 'GET,POST',
    credentials: true
  }
})

| Option | Type | Default | Description | |--------|------|---------|-------------| | options | ConstructorOptions | - | PgBoss constructor options | | prefix | string | /api | URL prefix for all API routes | | port | number | 3000 | Listening port | | hostname | string | localhost | Listening hostname | | env | Record<string, string> | process.env | Environment variables | | middleware | MiddlewareHandler \| MiddlewareHandler[] | - | Hono middleware to apply to API routes | | requestLogger | boolean | true | Enable/disable default request logging middleware | | logFormat | 'text' \| 'json' | text | Log output format | | exposeErrors | boolean | false | Return actual error messages to clients | | bodyLimit | number | 1048576 (1MB) | Max request body size in bytes | | routes.allow | string[] | all | List of pg-boss methods to expose | | routes.deny | string[] | none | List of pg-boss methods to exclude | | pages.root | boolean | true | Enable/disable the root page (/) | | pages.docs | boolean | true | Enable/disable Swagger docs (/docs) | | pages.openapi | boolean | true | Enable/disable OpenAPI spec (/openapi.json) | | auth.username | string | - | Basic auth username | | auth.password | string | - | Basic auth password | | cors.origin | string | - | CORS allowed origins | | cors.methods | string | GET,POST,PUT,DELETE,PATCH,OPTIONS | CORS allowed methods | | cors.headers | string | Content-Type,Authorization | CORS allowed headers |

Environment Variables

Alternatively, configure everything via environment variables:

| Variable | Default | Description | |---|---|---| | DATABASE_URL | - | PostgreSQL connection string | | PORT | 3000 | Listening port | | HOST | localhost | Listening hostname | | PGBOSS_PROXY_PREFIX | /api | URL prefix for API routes | | PGBOSS_PROXY_REQUEST_LOGGER | true | Enable request logging | | PGBOSS_PROXY_LOG_FORMAT | text | Log format: text or json | | PGBOSS_PROXY_EXPOSE_ERRORS | false | Return actual error messages to clients | | PGBOSS_PROXY_BODY_LIMIT | 1048576 | Max request body size in bytes | | PGBOSS_PROXY_ROUTES_ALLOW | all | Comma-separated list of routes to expose | | PGBOSS_PROXY_ROUTES_DENY | none | Comma-separated list of routes to exclude | | PGBOSS_PROXY_PAGE_ROOT | true | Enable root page | | PGBOSS_PROXY_PAGE_DOCS | true | Enable Swagger docs | | PGBOSS_PROXY_PAGE_OPENAPI | true | Enable OpenAPI spec | | Authentication | | | | PGBOSS_PROXY_AUTH_USERNAME | - | Basic auth username (must be set with password) | | PGBOSS_PROXY_AUTH_PASSWORD | - | Basic auth password (must be set with username) | | CORS | | | | PGBOSS_PROXY_CORS_ORIGIN | - | CORS allowed origins (comma-separated or *) | | PGBOSS_PROXY_CORS_METHODS | GET,POST,PUT,DELETE,PATCH,OPTIONS | CORS allowed methods | | PGBOSS_PROXY_CORS_HEADERS | Content-Type,Authorization | CORS allowed headers | | PGBOSS_PROXY_CORS_EXPOSE_HEADERS | - | CORS exposed headers | | PGBOSS_PROXY_CORS_CREDENTIALS | false | CORS allow credentials | | PGBOSS_PROXY_CORS_MAX_AGE | - | CORS preflight cache duration (seconds) |

PgBoss Constructor Options

You can pass any PgBoss constructor options via the options object:

const { app, boss } = await createProxyService({
  options: {
    connectionString: 'postgres://user:pass@host/database',
    schema: 'custom',
    supervise: true,    // enable job supervision (disabled by default)
    schedule: true,     // enable job creation by monitoring cron schedules (disabled by default)
    migrate: true       // run migrations on startup if needed (disabled by default)
  }
})

By default, supervise, schedule, and migrate are set to false to run the proxy in a stateless manner. Set any of these to true to enable that functionality.

Authentication

Basic auth can be enabled via environment variables:

PGBOSS_PROXY_AUTH_USERNAME=admin
PGBOSS_PROXY_AUTH_PASSWORD=secret

Both variables must be set together. When enabled, auth is applied to all routes under the prefix (e.g., /api/*). The root page (/), Swagger docs (/docs), and OpenAPI spec (/openapi.json) sit outside the prefix and remain publicly accessible.

CORS

CORS can be enabled via environment variables:

# Required: comma-separated list of allowed origins (use "*" for any)
PGBOSS_PROXY_CORS_ORIGIN=https://example.com,https://app.example.com

# Optional: allowed HTTP methods (default: GET, POST, PUT, DELETE, PATCH, OPTIONS)
PGBOSS_PROXY_CORS_METHODS=GET,POST,PUT,DELETE

# Optional: allowed request headers (default: Content-Type, Authorization)
PGBOSS_PROXY_CORS_HEADERS=Content-Type,Authorization,X-Custom-Header

# Optional: headers exposed to the client (default: none)
PGBOSS_PROXY_CORS_EXPOSE_HEADERS=X-Request-Id

# Optional: allow credentials (default: false)
PGBOSS_PROXY_CORS_CREDENTIALS=true

# Optional: preflight cache duration in seconds (default: none)
PGBOSS_PROXY_CORS_MAX_AGE=3600

When PGBOSS_PROXY_CORS_ORIGIN is set, CORS middleware is applied to all routes under the prefix. The root page and docs remain unaffected.

Custom Middleware

You can add custom Hono middleware to the API routes:

import { secureHeaders } from 'hono/secure-headers'

const { app, boss } = await createProxyService({
  options: { connectionString: 'postgres://user:pass@host/database' },
  middleware: [
    secureHeaders({
      xFrameOptions: false,
      xXssProtection: false
    })
  ]
})

Custom PgBoss Factory

For advanced customization, you can provide a custom bossFactory function to wrap or modify pg-boss behavior:

import { PgBoss } from 'pg-boss'

const { app, boss } = await createProxyService({
  bossFactory: (options) => {
    const instance = new PgBoss({
      ...options,
      // Custom configuration
    })

    // Wrap methods with logging
    const originalSend = instance.send.bind(instance)
    instance.send = async (...args) => {
      console.log('send called with:', args)
      return originalSend(...args)
    }

    return instance
  }
})

await boss.start()

Route Filtering

You can allowlist or denylist pg-boss methods to control which API routes are exposed:

const { app, boss } = await createProxyService({
  options: { connectionString: 'postgres://user:pass@host/database' },
  routes: {
    // Only expose safe operations (default: all methods are exposed)
    allow: ['send', 'fetch', 'complete', 'fail', 'getQueue', 'getQueues']
  }
})

Or deny specific methods:

const { app, boss } = await createProxyService({
  options: { connectionString: 'postgres://user:pass@host/database' },
  routes: {
    // Exclude destructive operations
    deny: ['deleteQueue', 'deleteAllJobs', 'deleteStoredJobs']
  }
})

Disabling Pages

You can disable the root page, docs, or OpenAPI spec:

const { app, boss } = await createProxyService({
  options: { connectionString: 'postgres://user:pass@host/database' },
  pages: {
    root: false,      // Disable the home page
    docs: false,      // Disable Swagger UI
    openapi: false    // Disable OpenAPI JSON endpoint
  }
})

Running from Source

# Start dev server
DATABASE_URL=postgres://user:pass@host/database npm run dev

# With custom port
PORT=8080 DATABASE_URL=postgres://user:pass@host/database npm run dev

# With authentication
DATABASE_URL=postgres://user:pass@host/database \
PGBOSS_PROXY_AUTH_USERNAME=admin \
PGBOSS_PROXY_AUTH_PASSWORD=secret \
npm run dev

# Build for production
npm run build

# Start production server
npm start

Docker

FROM node:24
WORKDIR /app
RUN npm install -g @pg-boss/proxy
ENV PORT=3000
EXPOSE 3000
CMD ["pg-boss-proxy"]
docker build -t pgboss-proxy .
docker run -d \
  -e DATABASE_URL="postgres://user:pass@host:5432/db" \
  -e PGBOSS_PROXY_AUTH_USERNAME=admin \
  -e PGBOSS_PROXY_AUTH_PASSWORD=secret \
  -e PGBOSS_PROXY_CORS_ORIGIN="https://myapp.com" \
  -p 3000:3000 \
  pgboss-proxy

Docker Compose

services:
  proxy:
    image: node:24
    working_dir: /app
    command: sh -c "npm install -g @pg-boss/proxy && pgboss-proxy"
    environment:
      DATABASE_URL: postgres://user:pass@db:5432/mydb
      PGBOSS_SCHEMA: pgboss
      PORT: 3000
      PGBOSS_PROXY_REQUEST_LOGGER: "true"
      PGBOSS_PROXY_LOG_FORMAT: "json"
      PGBOSS_PROXY_AUTH_USERNAME: admin
      PGBOSS_PROXY_AUTH_PASSWORD: secret
      PGBOSS_PROXY_CORS_ORIGIN: "https://myapp.com"
    ports:
      - "3000:3000"
    depends_on:
      - db

  db:
    image: postgres:16
    environment:
      POSTGRES_USER: user
      POSTGRES_PASSWORD: pass
      POSTGRES_DB: mydb
    ports:
      - "5432:5432"

API Reference