Going Insane -- Vercel Not Recognizing Environment Variable
Answered
Great black wasp posted this in #help-forum
Great black waspOP
The env variable was added 3 deployments ago (first pic).
Yet my build keeps failing due to that environment variable being undefined instead of a string (second pic).
I am going insane thinking about can possibly causing this. Please help.
Yet my build keeps failing due to that environment variable being undefined instead of a string (second pic).
I am going insane thinking about can possibly causing this. Please help.
Answered by riské
Im guessing you are using turborepo, are you maybe using strict env var mode & not specified the database_url there?
https://turborepo.com/docs/crafting-your-repository/using-environment-variables#strict-mode
https://turborepo.com/docs/crafting-your-repository/using-environment-variables#strict-mode
7 Replies
Im guessing you are using turborepo, are you maybe using strict env var mode & not specified the database_url there?
https://turborepo.com/docs/crafting-your-repository/using-environment-variables#strict-mode
https://turborepo.com/docs/crafting-your-repository/using-environment-variables#strict-mode
Answer
@riské Im guessing you are using turborepo, are you maybe using strict env var mode & not specified the database_url there?
https://turborepo.com/docs/crafting-your-repository/using-environment-variables#strict-mode
Great black waspOP
that's a really good call. i guess i'm a little confused -- i read the article and see the example in the first pic. the second pic is my turbo.json at the root. i have no env variables locally at the root, and only in the
the vercel deployment is set to that folder (3rd pic)
am i missing something?
/apps/web
folderthe vercel deployment is set to that folder (3rd pic)
am i missing something?
basically by default it doesnt pass the env vars
Great black waspOP
oh wow that actually worked to fix that error, thanks! super weird
yay
im surprised its so undocumented