Node version management

[xyzhuo]

Describe the bug

The installation of node is experiencing slow network issues. Is there a download cache directory for node? I noticed that every time I execute vp create, a temporary directory is created in the js_runtime directory. I am unable to place the already downloaded node installation package into the current temporary directory. After executing vp env off, executing vp create also results in the installation of node, but I have node managed by nvm globally.

Reproduction

Environment installation issue

Steps to reproduce

1. Running curl -fsSL https://vite.plus | bash keeps displaying "Setting up", but vp.exe is already present
2. I have completed the first step of installation
3. Configure the path environment traversal for system vp
4. Execute "vp create", and node will be installed once it runs
5. Executing "vp env off" has no effect

System Info

PS E:\> vp --version
VITE+ - The Unified Toolchain for the Web

vp v0.1.14

�[94m�[1mLocal vite-plus:�[0m�[39m
  �[94mvite-plus�[39m  Not found

�[94m�[1mTools:�[0m�[39m
  �[94mvite�[39m             Not found
  �[94mrolldown�[39m         Not found
  �[94mvitest�[39m           Not found
  �[94moxfmt�[39m            Not found
  �[94moxlint�[39m           Not found
  �[94moxlint-tsgolint�[39m  Not found
  �[94mtsdown�[39m           Not found

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.

[fengmk2]

vp env off currently only reverts the global node cli to the system-installed version. However, the node version used in the project does not revert.
There has been similar issue feedback, you can check the response at #977 (comment). We will follow up here and improve the functionality of vp env off to completely turn off the node version management capability.