Drizzle Kit dotenv support

[AlexBlokh]

As of now drizzle-kit config will be automatically supplied with .env file via backed in dotenv package.

In the next version kit will consume .env* files based on NODE_ENV and will be compatible with Bun env consumption. Kit will not consume dotenv files when run in Bun, since Bun already does:

we will read the following files automatically (listed in order of increasing precedence)

• .env
• .env.production .env.development .env.test (depending on value of NODE_ENV)
• .env.local

we will support variables expansion:

DB_USER=postgres
DB_PASSWORD=secret
DB_HOST=localhost
DB_PORT=5432
DB_URL=postgres://$DB_USER:$DB_PASSWORD@$DB_HOST:$DB_PORT/$DB_NAME

you will have an ability to provide custom env file or multiple files or tell Drizzle to not consume files automatically
drizzle-kit --env-file=.env.custom
drizzle-kit --env-file=.env.custom --env-file=.env.custom2
drizzle-kit --no-env -> load custom/yourself

UPD 05.11.24:
pending Bun fix, for now we'll use dotenvx for every runtime

[nguyendv]

Love it! Do we have a way to track when will this dotenv support land?

[kravetsone]

Why not use built-in Node.js features?

[jbergstroem]

I'd advise against using NODE_ENV values to branch. Its actually covered in the "best practices" around node.js/js development: https://www.platformatichq.com/node-principles#always-set-node_env=production - also in a podcast format here: https://changelog.com/jsparty/347

[Ashvith10]

@AlexBlokh has the support been added? Because it doesn't seem to be working for me locally, even after adding @next/env. After adding @next/env, only .env, .env.local, .env.production and .env.production.local is detected.

[do-adams]

Nice. It's working for me out of the box without a dotenv pkg dependency, so that's super cool!

It'd be nice to update the Drizzle tutorials to reflect this 🙌