Warn when the user install the local cli globally

[liangmiQwQ]

Description

For some persons who don't know Vite+ from the official website, they may easily run npm -g install vite-plus to install Vite+, but it is actually not the expected global CLI. Node management and other core features are missing.

Suggested solution

Print a warning when Vite+ local cli package is installed globally.

Alternative

N / A

Additional context

N / A

https://discord.com/channels/1475973262193459293/1524301479794446488/1524365671620804659

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.

[jong-kyung]

Maybe the JS bin.ts could detect commands that require the standalone Rust vp binary and show a clearer error when the package is installed globally. That would help explain why features like Node management are unavailable and point users to the intended global CLI install path 🤔

[jong-kyung]

with pnpm enable-global-virtual-store, local installs may run from a global-store realpath, so a naive global-install check could warn on every run.

[liangmiQwQ]

with pnpm enable-global-virtual-store, local installs may run from a global-store realpath, so a naive global-install check could warn on every run.

Good point. I'm thinking about how to deal with it...

Maybe the JS bin.ts could detect commands that require the standalone Rust vp binary and show a clearer error when the package is installed globally. That would help explain why features like Node management are unavailable and point users to the intended global CLI install path 🤔

It might be okay, but It's still better to print warnings for all commands when finding the vite-plus is installed globally (if possible). Considering installing the local CLI package globally can affect more than a few specific commands. There may also be behavior differences around shims, binaries, and delegation to the local CLI.

[jong-kyung]

It might be okay, but It's still better to print warnings for all commands when finding the vite-plus is installed globally (if possible). Considering installing the local CLI package globally can affect more than a few specific commands. There may also be behavior differences around shims, binaries, and delegation to the local CLI.

This seems a bit more complicated than it first appears... I also think your suggested warning is probably the best direction, but pnpm makes the detection more subtle 🫠

[liangmiQwQ]

Yeah, honestly. I have one approach in mind. When loading local Vite+ package, we could scan PATH to find the shell-level vp binary, excludes (node_modules/.bin), and check whether the binary is under VP_HOME. If it does, we can treat it as installed correctly without doubt. Otherwise, we can check whether vp env is usable. But I am not sure whether it is fully performance-wise because of the PATH scaning.

[jong-kyung]

Maybe the simplest approach is for the standalone Rust vp to set a small env marker when it delegates to the JS CLI. Then bin.ts can use that marker to avoid false warnings and show a clearer message only when needed. WDYT?

Ah, never mind. I think this would make the logic more complicated..