Does not install the 'latest' Node.js version

[jonkoops]

Describe the bug

When running vp env install latest or vp env default latest Node.js 24 is installed. However, at the time of writing the 'latest' version of Node.js is actually 25.

Reproduction

N/A

Steps to reproduce

1. vp env install latest
2. Observe the LTS version is installed instead.

System Info

Environment:
  Version  24.14.1
  Source   VITE_PLUS_NODE_VERSION

Tool Paths:
  node  /home/jon/.vite-plus/js_runtime/node/24.14.1/bin/node
  npm   /home/jon/.vite-plus/js_runtime/node/24.14.1/bin/npm
  npx   /home/jon/.vite-plus/js_runtime/node/24.14.1/bin/npx


vp v0.1.14

Local vite-plus:
  vite-plus  Not found

Tools:
  vite             Not found
  rolldown         Not found
  vitest           Not found
  oxfmt            Not found
  oxlint           Not found
  oxlint-tsgolint  Not found
  tsdown           Not found

Environment:
  Package manager  Not found
  Node.js          v24.14.1 (VITE_PLUS_NODE_VERSION)

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]

This is the logic currently specifically defined by Vite+, where latest represents the newest LTS version

[jonkoops]

I'd argue that is a counterintuitive choice. Considering the named options are 'lts' and 'latest', one would assume that 'lts' is the latest LTS and 'latest' is the latest released version (sans LTS).

[fengmk2]

@cpojer @TheAlexLichter do you have any suggestions?

[TheAlexLichter]

I agree with @jonkoops. LTS !== Latest and latest should be the actual latest version (so, odd-numbered if available).

Luckily this won't be an issue in the future given that Node changed their release schedule. (will still be relevant as they don't promote latest to LTS right away).

[jonkoops]

Thanks for the fix!