You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before reporting a bug I'm going to ask first. I'm using vercel cli with vercel dev to test a serverles function on local. When I launch vercel dev on the terminal, it acknowledges the .env.local file info - Loaded env from /user/someone/project/.env.local, but on the function side process.env.VARIABLE returns undefined.
What's even more weird is that doing an export VARIABLE and then launching vercel dev (or passing the env var on the command line) just works. It seems that is not really reading from the .env.local file to me, but maybe is there something I don't know about this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Before reporting a bug I'm going to ask first. I'm using vercel cli with vercel dev to test a serverles function on local. When I launch
vercel devon the terminal, it acknowledges the .env.local fileinfo - Loaded env from /user/someone/project/.env.local, but on the function side process.env.VARIABLE returns undefined.What's even more weird is that doing an export VARIABLE and then launching vercel dev (or passing the env var on the command line) just works. It seems that is not really reading from the .env.local file to me, but maybe is there something I don't know about this?
Beta Was this translation helpful? Give feedback.
All reactions