Problem
#1074 and #1166 already rename environment variables which begin with VITE_PLUS_ to VP_. However, there are still some env variables that start VITE_, influencing users' daily using.
List
| Original Name |
New Name |
Description |
VITE_GIT_HOOKS |
VP_GIT_HOOKS |
Vite+ only env vars, for git hooks behavior |
VITE_LOG |
VP_LOG |
Vite+ only, define log level |
VITE_GLOBAL_CLI_JS_SCRIPTS_DIR |
VP_GLOBAL_CLI_JS_SCRIPTS_DIR |
Vite+ only, mise compatibility |
Other env variables, like VITE_PACK_ should be treated as Vite itself's internal env vars, should not be changed.
Opening Questions / Trade-off
We either mark these changes as a breaking change like #1166 or still read the old names for compatibility. The former is simple but maybe influence version handling, the latter may leave legacy code forever.
/cc @jong-kyung
Problem
#1074 and #1166 already rename environment variables which begin with
VITE_PLUS_toVP_. However, there are still some env variables that startVITE_, influencing users' daily using.List
VITE_GIT_HOOKSVP_GIT_HOOKSVITE_LOGVP_LOGVITE_GLOBAL_CLI_JS_SCRIPTS_DIRVP_GLOBAL_CLI_JS_SCRIPTS_DIROther env variables, like
VITE_PACK_should be treated as Vite itself's internal env vars, should not be changed.Opening Questions / Trade-off
We either mark these changes as a breaking change like #1166 or still read the old names for compatibility. The former is simple but maybe influence version handling, the latter may leave legacy code forever.
/cc @jong-kyung