Multiple .env files in a monorepo

[gokaygurcan]

Multiple .env files in a monorepo

[juliusmarminge]

packages/api doesn't have any build step.

it also doesn't run any code on it's own right? so the next app will load the envs for you.

check out create-t3-turbo where i do this:

https://github.com/t3-oss/create-t3-turbo/blob/main/apps/nextjs/package.json#L7
https://github.com/t3-oss/create-t3-turbo/blob/main/packages/auth/env.ts
https://github.com/t3-oss/create-t3-turbo/blob/main/apps/nextjs/next.config.js#L7

[juliusmarminge]

{
  "scripts": {
    "with-env": "dotenv -e ../../.env --",
    "build": "pnpm with-env next build"
  }
}

should work

[gokaygurcan]

Hi @juliusmarminge,

Thanks for your reply.

I'm not sure about it. packages/api doesn't have any build step. This would work for apps/next for sure, and I tried similar things with dotenv and dotenv-expand, but it's not solving the issue I'm describing above I think.

In none of my attempts, I was able to make env.mjs in packages/api to read relevant values from root .env file.

[gokaygurcan]

Hi again,

I followed this approach and ended up in a very weird place now. It's working as expected here, https://codesandbox.io/p/devbox/ecstatic-pascal-wxcffg and not on my local machine. I guess for the sake of this issue, we can say it's no longer an issue. But it's still weird to get two different results with the very same code. I'll keep looking if I have something else installed that causes this discrepancy.

Thanks a lot, closing the issue now.

[gokaygurcan]

Update: eventually, i created a separate folder packages/env and moved everything under that. Instead of using it like import { env } from @/env.mjs i'm using it like import { env } from '@something/env now. Next step is to split it even further and import only relevant pieces if possible.

After trying a few options, this felt like the best approach so far. Throwing it here, in case someone needs any guidance in the future.