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
I would expect the rust runtime to act approximately like NextJS and load .env and .env.local when running the dev command.
However it only seems to pick environment variables from .env and not .env.local. It seems like this logic is located here in the vercel CLI and hard-coded. I assume this means the runtime is responsible for handling of any other .env files?
If that's the case, is there any chance we can export env variables defined in the process for use in the rust serverless functions, or manually pick up and export .env.local or similar?
The text was updated successfully, but these errors were encountered:
I would expect the rust runtime to act approximately like NextJS and load
.env
and.env.local
when running thedev
command.However it only seems to pick environment variables from
.env
and not.env.local
. It seems like this logic is located here in the vercel CLI and hard-coded. I assume this means the runtime is responsible for handling of any other.env
files?If that's the case, is there any chance we can export env variables defined in the process for use in the rust serverless functions, or manually pick up and export
.env.local
or similar?The text was updated successfully, but these errors were encountered: