Why was **VITE_PLUS_HOME** changed to **VP_HOME**?

[YaoweiZou]

Describe the bug

Some time ago I installed vite plus on my computer. I wanted to customize the installation location, and I guessed there might be some environment variable for that. I tried setting VITE_PLUS_HOME, and it worked. It felt very intuitive.

Today I installed vite plus on a new computer and again set VITE_PLUS_HOME, but it didn’t work. At first I thought the environment variable wasn’t configured correctly. I tried twice, but it still installed to the default location, which is the ~/.vite-plus directory. I figured something must have changed, so I checked the installation script and discovered that VITE_PLUS_HOME had been changed to VP_HOME.

Why was this done? It’s just an environment variable — readability is more important than length. “vite plus” is “vite plus”, not “vp”.

Reproduction

nothing

Steps to reproduce

No response

System Info

noting

Used Package Manager

npm

Logs

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.

[leaysgur]

Please see #1074

[fengmk2]

@YaoweiZou Sincerely apologize for any inconvenience this may cause you.

This is a breaking change. To avoid naming conflicts with Vite environment variable prefixes, we decided to make this modification.

[YaoweiZou]

Okay, I understand the reason now. I think VITEPLUS_HOME is better than VP_HOME, but since the change has already been made, it is what it is.