How to access environment variables in tanstack start in production mode?

[gerkim62]

in development mode the following code works, but in production it doesn't work as the variables are undefined

import { z } from "zod";

const EnvSchema = z.object({
  NODE_ENV: z.enum(["production", "development"]).default("development"),
  UPSTASH_REDIS_REST_URL: z.string().url(),
  UPSTASH_REDIS_REST_TOKEN: z.string(),
  UPLOADTHING_TOKEN: z.string(),
});

console.log(process.env, "process.env");
console.log(import.meta.env, "import.meta.env");
console.log(
  process.env["UPSTASH_REDIS_REST_URL"],
  "process.env.UPSTASH_REDIS_REST_URL"
);

export const env = EnvSchema.parse(process.env);

console.log(env, "env");

export default env;

while it works in dev mode, this is the error thrown when i try to access the variables after building and running pnpm start

undefined process.env.UPSTASH_REDIS_REST_URL
[nitro] [request error] [unhandled] [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "UPSTASH_REDIS_REST_URL"
    ],
    "message": "Required"
  },
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "UPSTASH_REDIS_REST_TOKEN"
    ],
    "message": "Required"
  },
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "UPLOADTHING_TOKEN"
    ],
    "message": "Required"
  }
]

[chinanderm]

@gerkim62 Did you figure out anything here? I'm running into the same issue. Values from .env work fine in dev mode but are undefined when running a production build.

[gerkim62]

i decided to move away and use NextJS instead.

[AhmedBaset]

Did you figure out anything here? I'm running into the same issue. Values from .env work fine in dev mode but are undefined when running a production build.

#3688 (comment)

[polyrenn]

In my case, I run my app in prod using pm2, so I pass in my envs using ecosystem.config.js, that makes my secret available when I run start.

[AhmedBaset]

In production TSS/vinxi doesn't load environment variables, you have to maintain them yourself.

node --env-file=".env" .output/server/index.mjs

If you're running a docker container:

CMD ["node", "--env-file=.env", ".output/server/index.mjs"]

If you're hosting on a serverless platform, it will mostly handle that for you.

This behavior is the same as Nuxt