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

@zetesis/payload-pgvector

v0.1.4

Published

A Payload CMS search adapter backed by Postgres + pgvector. Sibling of @zetesis/payload-typesense: implements the payload-indexer IndexerAdapter contract over pgvector, with app-side embeddings via any OpenAI-compatible endpoint (e.g. a LiteLLM gateway).

Readme

@zetesis/payload-pgvector

A Postgres + pgvector search backend for Payload CMS. Implements the @zetesis/payload-indexer IndexerAdapter contract — a sibling of @zetesis/payload-typesense — with app-side embeddings via any OpenAI-compatible endpoint (OpenAI, a LiteLLM gateway, a local TEI/Ollama server, …). Unlike Typesense, pgvector does not embed for you: vectors are produced app-side before they hit the database.

Install

pnpm add @zetesis/payload-pgvector @zetesis/payload-indexer pg

Requires the vector extension and a dedicated schema (never public, so a Payload/Drizzle schema push can't treat the raw tables as unmanaged and drop them):

CREATE EXTENSION IF NOT EXISTS vector;
CREATE SCHEMA IF NOT EXISTS pgvector;

Usage

import { createPgvectorAdapter, createPgvectorPlugin } from '@zetesis/payload-pgvector'
import { createIndexerPlugin } from '@zetesis/payload-indexer'

const adapter = createPgvectorAdapter({
  connectionString: process.env.DATABASE_URL!,
  schema: 'pgvector', // required, dedicated
  embedding: {
    baseUrl: process.env.LITELLM_PROXY_URL!, // any OpenAI-compatible /embeddings
    apiKey: process.env.EMBEDDINGS_API_KEY!,
    model: 'text-embedding-3-small',
    dimensions: 1536,
    sendDimensions: true // text-embedding-3-* honour it; off for ada-002/TEI/Ollama
  }
})

// Document sync (hooks) + schema sync (ensure tables on init):
const { plugin: indexerPlugin } = createIndexerPlugin({ adapter, features: { sync: { enabled: true } }, collections })
const schemaPlugin = createPgvectorPlugin({ adapter, collections, dimensions: 1536 })
// add both to your Payload `plugins`

Query (read-only consumers, e.g. an MCP server):

const hits = await adapter.searchByText('posts_chunk', 'justicia sin estado', { limit: 10 })

Notes

  • Atomic reindex: replaceDocumentsByFilter embeds before deleting and runs delete+insert in one transaction, so a failed reindex never wipes the old index.
  • Schema sync is additive (CREATE/ADD … IF NOT EXISTS) and warns on incompatible drift (vector dimension / HNSW distance) — change those by dropping & recreating.
  • Index-time and query-time must use the same model + dimensions, or similarity is garbage.