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
However as you can see it imports VERCEL_ from private, which is not accessible on the client code. And there's no VECEL_ exported variables in public.
Unless I'm missing something, but it would be nice if Vercel started exposing public system variables again?
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
-
Idea
I think Vercel used to expose
VITE_
prefixed variables forv0
, however it doesn't seem to be supported in1.x
or2.x
anymore.Best I could come up with is keeping empty
VERCEL_
envs locally, andPUBLIC_APP_
envs in Vercel with a utility like this:However as you can see it imports
VERCEL_
fromprivate
, which is not accessible on the client code. And there's noVECEL_
exported variables inpublic
.Unless I'm missing something, but it would be nice if
Vercel
started exposing public system variables again?Beta Was this translation helpful? Give feedback.
All reactions