Installation via mise-en-place

[dtinth]

Description

I am using mise to manage all my toolchain right now. Currently, viteplus does not show up in registry, nor is there an easy way to install without running an installation script.

Suggested solution

It would be great if it’s possible to install the vp CLI via mise like mise use -g vite-plus or mise use -g vp.

The recommended method would be to put it in the aqua registry. Alternatively, mise can also install binaries from GitHub Releases, however Vite+ doesn’t publish binaries via GitHub Releases yet (right now binaries seems to be published on npm, however, I would not recommend using npm backend because it depends on Node.js, which vp intends to manage).

Alternative

Additional context

I tried using the http backend to install vp CLI directly from npm registry without going through npm CLI.

# ~/.config/mise/config.toml
[tools]
"http:vite-plus" = {
  version = "0.1.11",
  platforms = {
    macos-arm64 = { url = "https://registry.npmjs.org/@voidzero-dev/vite-plus-cli-darwin-arm64/-/vite-plus-cli-darwin-arm64-{{version}}.tgz" },
    macos-x64 = { url = "https://registry.npmjs.org/@voidzero-dev/vite-plus-cli-darwin-x64/-/vite-plus-cli-darwin-x64-{{version}}.tgz" },
    linux-x64 = { url = "https://registry.npmjs.org/@voidzero-dev/vite-plus-cli-linux-x64-gnu/-/vite-plus-cli-linux-x64-gnu-{{version}}.tgz" },
    linux-arm64 = { url = "https://registry.npmjs.org/@voidzero-dev/vite-plus-cli-linux-arm64-gnu/-/vite-plus-cli-linux-arm64-gnu-{{version}}.tgz" },
    windows-x64 = { url = "https://registry.npmjs.org/@voidzero-dev/vite-plus-cli-win32-x64-msvc/-/vite-plus-cli-win32-x64-msvc-{{version}}.tgz" },
    windows-arm64 = { url = "https://registry.npmjs.org/@voidzero-dev/vite-plus-cli-win32-arm64-msvc/-/vite-plus-cli-win32-arm64-msvc-{{version}}.tgz" }
  }
}

This is based on the description on the docs:

Vite+ ships in two parts: vp, the global command-line tool, and vite-plus, the local package installed in each project.

$ mise install
http:vite-plus@0.1.11 generate checksum vite-plus-cli-darwin-arm64-0.1.11.tgz
✅ Installed successfully. Confirmed vp binary is installed on both Mac and Linux.

$ vp help
VITE+ - The Unified Toolchain for the Web
✅ `vp help` works

$ vp create
node:internal/modules/cjs/loader:1459
  throw err;
  ^

Error: Cannot find module '/Users/dtinth/.local/share/mise/http-tarballs/node_modules/vite-plus/dist/bin.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1456:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1066:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1071:22)
    at Module._load (node:internal/modules/cjs/loader:1242:25)
    at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
    at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
    at node:internal/main/run_main_module:33:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v24.14.0
❌ `vp create` installs Node v24.14.0 correctly, but then crashes

$ mise uninstall http:vite-plus
🧹 Uninstall the `vp` CLI managed by mise (manually remove the config afterwards after running)

It seems like the vp CLI also kinda depends on the vite-plus npm package being installed globally which prevented this setup from working.

Validations

• Read the Contributing Guidelines.
• Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
• Check that there isn't already an issue requesting the same feature.

[fengmk2]

Because vp is also a Node.js runtime manager, installing vp through mise requires handling the Node.js runtime conflict issues involved.

[dtinth]

Just a bit of update on my investigation of v0.1.11, I am able to get Vite+ to run and build an app with the above mise configuration by doing this (tested on docker run -ti --rm debian:trixie with only mise installed and vp installed per above config):

# Manually create a folder for installing the global `vite-plus` package
mkdir ~/.vite-plus/0.1.11
env -C ~/.vite-plus/0.1.11 vp env exec npm init -y
env -C ~/.vite-plus/0.1.11 vp env exec npm install vite-plus@0.1.11

Then add to ~/.config/mise/config.toml:

[env]
VITE_GLOBAL_CLI_JS_SCRIPTS_DIR = "{{ env.HOME }}/.vite-plus/0.1.11/node_modules/vite-plus/dist"

Thankfully, Vite+ allows the Global CLI JS directory to be overridden via env var. So now vp dev, vp build, vp test, vp lint works ✅.

However, the node, npm, npx, vpx shims are not working, as it seems to be hardcoded to symlink to ../current/bin/vp.

# ls -l ~/.vite-plus/bin/
total 4
lrwxrwxrwx 1 root root  17 Mar 16 08:45 node -> ../current/bin/vp
lrwxrwxrwx 1 root root  17 Mar 16 08:45 npm -> ../current/bin/vp
lrwxrwxrwx 1 root root  17 Mar 16 08:45 npx -> ../current/bin/vp
lrwxrwxrwx 1 root root  17 Mar 16 08:45 vp -> ../current/bin/vp
-rw-r--r-- 1 root root 158 Mar 16 08:59 vp-use.cmd
lrwxrwxrwx 1 root root  17 Mar 16 08:45 vpx -> ../current/bin/vp

However, vp env exec node works works well ✅ (I am fine with that, now all JS-related stuff really goes through vp CLI).

We can manually create shims though:

# cd "$(dirname "$(mise which vp)")"
# ln -s vp vpx
# ln -s vp node
# ln -s vp npm
# ln -s vp npx
# mise reshim

After this, we can directly run Node.

# node
Welcome to Node.js v24.14.0.
Type ".help" for more information.
>

IMO, if we don't install Node.js via Mise and just use vp instead, then there is no conflict.

[nwidynski]

Is there a reason why you don't want to carry vite-plus as a package dependency? Since you are already managing node with mise anyways, I'm not sure what the advantage of installing it via http backend would be over adding it to package.json.

[merodiro]

When I installed it using npm backend

[tools]
"npm:vite-plus" = "latest" 

It mostly worked but vp test fail without any obvious errors. but when I used http backend as mentioned here it worked. not sure what is the difference

[nwidynski]

I meant adding vite-plus as a normal package.json dev dependency. Why are you managing it via mise? You dont need vp env or vp migrate if you manage idiomatic node versions with mise anyways.

"devDependencies": {
  "vite-plus": "latest",
  "@voidzero-dev/vite-plus-core": "latest"
},
"overrides": {
  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
  "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
}

[markmals]

@nwidynski the local installation via npm doesn't include a lot of the commands, such as vp add, vp remove, vpx, etc.

I've created my own plugin for Mise in the meantime. You can use it like so:

[plugins]
vite-plus = "https://github.com/markmals/mise-vite-plus"

[tools]
vite-plus = "latest"