inland tinsel
Hey guys, there have been a lot of changes to vinxi, nitro and I am wondering as of the latest tanstack start version how we should go about injecting our environment variables server side.
I can pass them through to vite just fine, using VITE_ prefix but when it comes to getting my server side env variables, I cannot find a solution.
It seems to work in dev just fine, but not in production
vivid scaffold
how are you reading your env vars ?
import.meta.env on the client
process.env on the server
const config = defineConfig(async ({ mode }) => {
process.env = {
...process.env,
...import.meta.env,
...loadEnv(mode, process.cwd(), ''),
}
~~~~
i also added this at the beginning of my vite.config.ts file
steep forge
I am also experiencing some issue about this. The env on my prisma after building cannot be read.
After building the app this the error
error: Environment variable not found: VITE_DATABASE_URL.
--> schema.prisma:14
|
13 | provider = "postgresql"
14 | url = env("VITE_DATABASE_URL")
|
uh, your database URL should probably NOT be a public env var
VITE_* vars are public and bundled at build time
you can see them as build time macros
steep forge
I already use also the Not VITE . I first used process.env.DATABASE_URL! on an .env file. Still getting the same error
steep forge
how are you setting the env in prod ?
I directly put the url of my db. Since this project is for local atm.
steep forge
and how are you running the prod build
I followed the instruction to run node .output/server/index.mjs
I used TurboRepo for building prod
I am using prisma-orm btw
Turbo.json
{
"$schema": "https://turbo.build/schema.json",
"ui": "tui",
"tasks": {
"build": {
"dependsOn": ["^build"],
"inputs": ["$TURBO_DEFAULT$", ".env*"],
"outputs": ["dist/**"],
"env": ["DATABASE_URL"]
},
"lint": {
"dependsOn": ["^lint"]
},
"check-types": {
"dependsOn": ["^check-types"]
},
"dev": {
"cache": false,
"persistent": true
},
"db:generate": {
"cache": false
},
"db:migrate": {
"cache": false,
"persistent": true
},
"db:deploy": {
"cache": false
}
}
}
no i mean, WHERE is this set
also this doesnt make sense
you dont need the db url to build
it shouldnt be bundled in your build
because it should be read at runtime (not build time)
steep forge
I followed the instructions from Prisma Docs about TurboRepo
steep forge
Does my Project set-up is wrong base on my turbo.json?
the .env is on apps/wed directory.
vivid scaffold
ah
i think that's the issue
see your .env* path
maybe try
apps/web/.env*
or maybe **/.env*
(i doubt the second works)
steep forge
Do I need to set this also?
const config = defineConfig(async ({ mode }) => {
process.env = {
...process.env,
...import.meta.env,
...loadEnv(mode, process.cwd(), ''),
}
~~~~
in my vite.config?
vivid scaffold
not sure, but i would think so
steep forge
OH! NICELY DONE! Thank you!!
steep forge
or maybe `**/.env*`
This one solves the issue!
vivid scaffold
great
glad i could help
@steep forge although do note that this is potentially problematic: you'll be reading ALL env files in the monorepo. You could have multiple env files with multiple DATABASE_URL, which will cause conflicts
not sure what the best solution is in this scenario, but i would assume prefixing your variable names could be an idea
steep forge
Sorry but the one that I tested was a cached of the build with direct inject url in prisma schema. Now that I try to build again. The errors comes back and I again direct inject the db url in prisma schema. I don't know the problem in reading the env files in the server side. I also tried Drizzle ORM still getting the same error :: Cannot read env vars in runtime
vivid scaffold
Sorry but the one that I tested was a cached of the build with direct inject url...
instead of **/.env* have you tried apps/web/.env* ?
steep forge
Yes! I have tried that too.
steep forge
```ts
const config = defineConfig(async ({ mode }) => {
process.env = {
.....
What does this do when you add this on config?
Maybe for the meantime I will opt-out or cover my db-url in prisma schema before commtting to git.
vivid scaffold
What does this do when you add this on config?
loadEnv forces vite to load the runtime env, and then it is set into process.env
steep forge
loadEnv forces vite to load the runtime env, and then it is set into process.env
This only works if using vite build? But no in turbo build?
vivid scaffold
your turbo builds seems to run the build task of your apps/web subrepo
or, at least, it should
which should be something like vite build
mine's this:
"build": "cross-env NODE_ENV=production BUILD_ENV=production vite build",
because i do things during build that require those vars
in fact, here are dev/start/build for me
"dev": "vite dev --port 3000",
"start": "node --env-file-if-exists=.env .output/server/index.mjs",
"build": "cross-env NODE_ENV=production BUILD_ENV=production vite build",
the start command explicitely loads the .env file
but this shouldn't matter to you as your issue happens at build time if i understood correctly
what happens if you remove the dependency on DATABASE_URL @steep forge
as in, here
if you have "env": [] instead
steep forge
as in, here
Nothing change it’s. I just tried to remove and put it back again. Doesnt change anything. Maybe Ill just remove turbo and use vite for build
vivid scaffold
are you planning on making a real monorepo ?
as in, a lot of apps and libs inside a single repo ?
if no, yeah, don’t bother too much with turborepo
and even if you need to have a monorepo, i find Nx to be more robust and less Vercel biased