DT

Drizzle Team•2y ago

ahylianhuman

drizzle-kit should use `peerDependencies` instead of bundling dependencies

In addition to helpdrizzle-kit overriding `process.env` before `@next/env` can load values for local development, I see that drizzle-kitdrizzle-kit has bundled a bunch of drivers into its own executable instead of using peerDependenciespeerDependencies. This makes it impossible to override neonConfigneonConfig settings so I can use a local wsproxywsproxy for local development since drizzle-kitdrizzle-kit is using an entirely separate and unexported copy of @vercel/postgres@vercel/postgres and @neondatabase/serverless@neondatabase/serverless.

There should either be a way to configure settings on the bundled copy @neondatabase/serverless@neondatabase/serverless or a way to use peerDependenciespeerDependencies to dedupe drivers so that we can override settings on the same instance that drizzle-kitdrizzle-kit uses.

Running Vercel Postgres Locally

The setup I use for local work with Vercel Postgres or Neon database

GitHub

serverless/CONFIG.md at main · neondatabase/serverless

Connect to Neon PostgreSQL from serverless/worker/edge functions - neondatabase/serverless