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
import dotEnvExtended from 'dotenv-extended';
dotEnvExtended.load({includeProcessEnv: true, errorOnMissing: true, errorOnExtra: false});
Reading the documentation there shouldn't be an error as the ìncludeProcessEnv put together variables from process.env, .env and .env.defaults. So in this case the addition is the same as the .env.schema requirement.
The only way I managed to avoid the error is by copying .env.schema to .env.defaults.
It think this is a bug of the library that should be fixed as the schema should be validated against the addition of process.env and the files.
The text was updated successfully, but these errors were encountered:
Please remove the issue as it may mislead other developers. It's being my fault. I didn't notice that I have two places in the code retrieving the configuration and in one of them I haven't include the includeProcessEnv: true
I was going to write about this issue as a bug in the library that is closely related with the answer to issue #35.
In my code I have:
Reading the documentation there shouldn't be an error as the
ìncludeProcessEnv
put together variables fromprocess.env
,.env
and.env.defaults
. So in this case the addition is the same as the.env.schema
requirement.The only way I managed to avoid the error is by copying
.env.schema
to.env.defaults
.It think this is a bug of the library that should be fixed as the schema should be validated against the addition of
process.env
and the files.The text was updated successfully, but these errors were encountered: