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
interfaceUserConfig{/** * The directory in which the `.env` files will be searched. * Set to `false` to disable `.env` files * @default Project root */envRoot?: string|false}
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There are a number of scenarios when
.env
files location and vite-root must be different:.env
files are common.I feel the need to specify in the configuration where to look for an
.env
files:I propose add
envRoot
parameterAnd
inlineConfig.envFile
will be deprecatedAs a workaround, at the moment, you have to use
loadEnv
from vite to load.env
files and set the values inprocess.env
manually.Beta Was this translation helpful? Give feedback.
All reactions