@vercel/postgres 0.1.0-canary.7

Connect to Vercel Postgres databases on the Edge

@vercel/postgres@0.1.0-canary.7 was published on 2023-04-26. Its manifest declares 1 runtime dependency and 1 peer requirement. 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.1.0-canary.7 · View npm registry JSON · Latest release

Package specifications

Version0.1.0-canary.7
License declarationMIT
Published2023-04-26T13:17:17.212Z
Node.js requirement>=14.6
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size13.56 KiB
Published file count7
Package typemodule
ES module entry./dist/index.js
Default entry./dist/index.cjs
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies1
Repository stars599
Repository forks104

Install @vercel/postgres 0.1.0-canary.7

npm install @vercel/postgres@0.1.0-canary.7
pnpm add @vercel/postgres@0.1.0-canary.7
yarn add @vercel/postgres@0.1.0-canary.7

Runtime dependencies

Peer requirements

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