1 reply

drizzle-kit overriding `process.env` before `@next/env` can load values

ahylianhuman · 2024-07-27T22:24:15.268Z

I'm trying to use `drizzle-kit push` using the setup recommended by the [Drizzle](https://orm.drizzle.team/docs/get-started-postgresql#vercel-postgres) and [Vercel](https://vercel.com/docs/storage/vercel-postgres/using-an-orm#drizzle) docs, but I am finding that the `drizzle-kit` command is performing its own `dotenv` loading before my config file can import and use `loadEnvConfig` from `@next/env`. This is causing issues if I have an empty value for `POSTGRES_URL` in `.env` (for documentation purposes) and the actual value in `.env.local` (for local development) because `drizzle-kit` is unaware of how [`@next/env` loads environment variables](https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables). I've worked around this issue by setting by setting `DOTENV_CONFIG_PATH=/dev/null`, but there should a way to turn this automatic behavior off (or more ideally, make it opt-in instead of opt-out) so it is easier to load environment variables correctly using `@next/env` or another `.env` loader of choice.

I'm trying to use

drizzle-kit push

drizzle-kit push

using the setup recommended by the Drizzle and Vercel docs, but I am finding that the

drizzle-kit

drizzle-kit

command is performing its own

dotenv

dotenv

loading before my config file can import and use

loadEnvConfig

loadEnvConfig

from

@next/env

@next/env

. This is causing issues if I have an empty value for

POSTGRES_URL

POSTGRES_URL

.env

.env

(for documentation purposes) and the actual value in

.env.local

.env.local

(for local development) because

drizzle-kit

drizzle-kit

is unaware of how

@next/env

@next/env

loads environment variables.

I've worked around this issue by setting by setting

DOTENV_CONFIG_PATH=/dev/null

DOTENV_CONFIG_PATH=/dev/null

, but there should a way to turn this automatic behavior off (or more ideally, make it opt-in instead of opt-out) so it is easier to load environment variables correctly using

@next/env

@next/env

or another

.env

.env

loader of choice.

Drizzle ORM - PostgreSQL

Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.

Using an ORM to access your Postgres database

Learn how to use your favorite ORM to access your database from your apps

Drizzle Team•2y ago•

1 reply

ahylianhuman

drizzle-kit overriding `process.env` before `@next/env` can load values

I'm trying to use

drizzle-kit push

drizzle-kit push

using the setup recommended by the Drizzle and Vercel docs, but I am finding that the

drizzle-kit

drizzle-kit

command is performing its own

dotenv

dotenv

loading before my config file can import and use

loadEnvConfig

loadEnvConfig

from

@next/env

@next/env

. This is causing issues if I have an empty value for

POSTGRES_URL

POSTGRES_URL

.env

.env

(for documentation purposes) and the actual value in

.env.local

.env.local

(for local development) because

drizzle-kit

drizzle-kit

is unaware of how

@next/env

@next/env

loads environment variables.

I've worked around this issue by setting by setting

DOTENV_CONFIG_PATH=/dev/null

DOTENV_CONFIG_PATH=/dev/null

, but there should a way to turn this automatic behavior off (or more ideally, make it opt-in instead of opt-out) so it is easier to load environment variables correctly using

@next/env

@next/env

or another

.env

.env

loader of choice.

Drizzle ORM - PostgreSQL

Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.

Using an ORM to access your Postgres database

Learn how to use your favorite ORM to access your database from your apps

drizzle-kit overriding `process.env` before `@next/env` can load values

drizzle-kit overriding `process.env` before `@next/env` can load values

Similar Threads

Similar Threads

Similar Threads