Change NODE_ENV convention

Any one could change the naming convention that comes with t3 stack latest version. By default is "NODE_ENV: z.enum(['development', 'test', 'production']).default("development")" i changed to NODE_ENV: z.enum(['dev', 'qa', 'production']).default("dev") but when i start with yarn start it telling me that is receiving "development" and also in .env file is NODE_ENV="dev" Any help pls
2 Replies
fl0w
fl0w9mo ago
lets say you start your nextjs server with "npm run dev" then node / next will override NODE_ENV to development, same for npm run build with production...
Rhys
Rhys8mo ago
@Casal0x id keep the NODE_ENV convention the same and just add a DEN_ENV var or something similar Libraries may depend on NODE_ENV being consistent, I’d avoid changing it
Want results from more Discord servers?
Add your server