1 reply

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

ahylianhuman · 2024-07-27T22:39:50.991Z

In addition to [the `.env` loading issue](https://discord.com/channels/1043890932593987624/1266883882985328690) for local development, I see that `drizzle-kit` has bundled a bunch of drivers into its own executable instead of using `peerDependencies`. This makes it impossible to [override `neonConfig` settings](https://github.com/neondatabase/serverless/blob/main/CONFIG.md#neonconfig-configuration) so I can use [a local `wsproxy` for local development](https://gal.hagever.com/posts/running-vercel-postgres-locally) since `drizzle-kit` is using an entirely separate and unexported copy of `@vercel/postgres` and `@neondatabase/serverless`. There should either be a way to configure settings on the bundled copy `@neondatabase/serverless` or a way to use `peerDependencies` to dedupe drivers so that we can override settings on the same instance that `drizzle-kit` uses.