@vercel/postgres 0.8.0

Connect to Vercel Postgres databases on the Edge

@vercel/postgres@0.8.0 was published on 2024-04-02. Its manifest declares 4 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=14.6.

Deprecated: @vercel/postgres is deprecated. If you are setting up a new database, you can choose an alternate storage solution from the Vercel Marketplace. If you had an existing Vercel Postgres database, it should have been migrated to Neon as a native Vercel integration. You can find more details and the guide to migrate to Neon's SDKs here: https://neon.com/docs/guides/vercel-postgres-transition-guide

All @vercel/postgres versions · Permanent reference to 0.8.0 · Latest release

Package specifications

Version0.8.0
License declarationApache-2.0
Published2024-04-02T07:51:51.402Z
Node.js requirement>=14.6
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size72.94 KiB
Published file count19
Package typemodule
ES module entry./dist/index.js
Default entry./dist/index.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies16
Repository stars600
Repository forks102

Install @vercel/postgres 0.8.0

npm install @vercel/postgres@0.8.0
pnpm add @vercel/postgres@0.8.0
yarn add @vercel/postgres@0.8.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness