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
We're currently investigating a possibility of supporting .env file natively in a Framework.
Main reason is that ideally env vars from .env should be loaded at very begin of a process, and resolution via plugin is delayed simply by its nature. So taking into account dotenv popularity I believe it's a good call to make it a first class citizen in the Framework (it's also already supported in Serverless Components)
Also we simply plan to support it it as convenient env vars transport into process.env and nothing more (no automatic leak into lambdas etc.)
Thanks @medikoo - I included my comments in that thread. I'm more than happy to be part of the conversation and will do my best to support your efforts.
@colynb great thanks for this plugin!
We're currently investigating a possibility of supporting
.env
file natively in a Framework.Main reason is that ideally env vars from
.env
should be loaded at very begin of a process, and resolution via plugin is delayed simply by its nature. So taking into account dotenv popularity I believe it's a good call to make it a first class citizen in the Framework (it's also already supported in Serverless Components)Also we simply plan to support it it as convenient env vars transport into
process.env
and nothing more (no automatic leak into lambdas etc.)We will value your feedback at serverless/serverless#7907
The text was updated successfully, but these errors were encountered: