Sourcemap Explorer
Stack · npm package

@vercel/postgres

Connect to Vercel Postgres databases on the Edge

latest 0.10.0· Apache-2.0· 47 versions publishedView on npm

About

Connect to Vercel Postgres databases on the Edge

Live mirror of the GitHub README. Updated whenever the repo's default branch changes.

Vercel Storage

Packages

Deprecated Packages

The packages @vercel/postgres and @vercel/kv have been deprecated and the associated products Vercel Postgres and Vercel KV no longer exist.

Note: You can install other postgres and KV storage solutions from the Vercel Marketplace as native integrations to your Vercel project.

The source code for these deprecated packages is preserved in the vercel-kv-vercel-postgres-archive branch.

Migration Guides

Quick facts

Latest version0.10.0
LicenseApache-2.0
Repositorygithub.com/vercel/storage
Homepagevercel.com
Installnpm install @vercel/postgres
Direct dependencies3

How Sourcemap Explorer detects @vercel/postgres

We catch @vercel/postgres from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@vercel/postgres/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

  1. 1

    Confirm the site exposes sourcemaps

    In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment.

  2. 2

    Find the package in the bundle

    Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@vercel/postgres/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@vercel/postgres/package.json` gives you the exact installed version.

  3. 3

    Read the version directly from package.json

    Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@vercel/postgres/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Recent versions

Version
Released
0.1.2
—
0.1.3
—
0.2.0
—
0.2.1
—
0.3.0
—
0.3.1
—
0.3.2
—
0.4.0
—

FAQ

What is @vercel/postgres used for?

Connect to Vercel Postgres databases on the Edge

How can I tell if a website is using @vercel/postgres?

Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@vercel/postgres` from two complementary signals: `node_modules/@vercel/postgres/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.

What is the latest version of @vercel/postgres?

0.10.0, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.

Where can I read more?

Project homepage: https://vercel.com. Source code: https://github.com/vercel/storage. Published on npm: https://www.npmjs.com/package/@vercel/postgres. Licensed as Apache-2.0.

Detected by Sourcemap Explorer

When a bundle ships sourcemaps, we read the embedded package.json for @vercel/postgres and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.

Install free on Chrome