Vite: VITE_ variables and build time

Variables that exist when Vite starts have the highest priority. A .env file does not replace them.

npx getmyenv run -- vite

run does not read .env files. Delete them when you are ready. Until you do, Vite still fills names the context does not set from them.

run passes every name to the Vite process. Vite exposes only the ones that start with VITE_, or your envPrefix.

js
const apiUrl = import.meta.env.VITE_API_URL;

Vite loads .env files only after it reads the config. With run, every name is already in process.env, including in vite.config.

vite build replaces import.meta.env.VITE_* with the values in the files it writes. Anyone who loads the site can read them. Build with the context you deploy. Production is Read-only, so the build machine needs a server token in GETMYENV_TOKEN:

npx getmyenv run production -- vite build

Keep API keys and other secrets out of VITE_ names. Call them from a server instead. set and import warn when a VITE_ name or value looks like a secret. A new value needs a new build.

npx getmyenv run production --explain -- vite build

npx getmyenv run --explain lists every name and where it comes from. Never values.