.env.local support maybe?

[bdrtsky]

Using Drizzle with Next.js, and it's loading .env.local. I know I can use dotenv but don't want to use another package. Could you maybe consider to add .env.local support for Drizzle Kit?

[nicholasdly]

Assuming you're trying to reference environment variables within drizzle.config.ts here, I'm pretty sure this is more on Next.js than it is on Drizzle. Environment variables in Next.js are only accessible within the Next.js runtime, and the root config file for Drizzle is loaded outside of that runtime.

You can use dotenv, but Next.js has a specific package for this: @next/env. See their documentation here.

After installing the package, you can load your environment variables within drizzle.config.ts and it should fix your problem.

import { loadEnvConfig } from '@next/env';
 
const projectDir = process.cwd();
loadEnvConfig(projectDir);

export default defineConfig({
  // ...
});

If you're using @t3-oss/env-nextjs for type-safe environment variables, you can use loadEnvConfig in a similar manner allowing you to use your type-safe env object instead of process.env within drizzle.config.ts.

[simply-solv-admin]

The issue I have found with supporting .env.local is when you try to access it in drizzle-kit. It works fine in my next app...

[nicholasdly]

Can you be more specific with how you're accessing environment variables in drizzle-kit? .env.local would naturally work fine within your Next.js app since it's inside the Next.js runtime.

[AlexBlokh]

this will be in the next release #3405

[Ashvith10]

@nicholasdly In my case, when I have both .env.development and .env.development.local, and it simply does not work. I've also tried test instead of development, and that also does not work. However, it works when I rename it to .env, .env.local, .env.production and .env.production.local ?