Skip to content

docs: add manual package-manager install path for vp#1116

Open
yash27-lab wants to merge 2 commits intovoidzero-dev:mainfrom
yash27-lab:codex/issue-896-manual-install-docs
Open

docs: add manual package-manager install path for vp#1116
yash27-lab wants to merge 2 commits intovoidzero-dev:mainfrom
yash27-lab:codex/issue-896-manual-install-docs

Conversation

@yash27-lab
Copy link

Summary

Add a manual package-manager-based installation path for vp to the docs.

Changes

  • add npm install -g vite-plus and pnpm add -g vite-plus to /guide/
  • add follow-up notes for PATH, pnpm setup, vp env setup, and vp env off
  • add matching npm/pnpm upgrade commands to /guide/upgrade

Verification

  • verified the docs gap still exists on current main
  • tested npm install -g vite-plus in an isolated temp prefix
  • tested pnpm add -g vite-plus in an isolated temp global environment
  • tested upgrade with:
    • npm install -g vite-plus@latest
    • pnpm add -g vite-plus@latest
  • ran cd docs && pnpm install && pnpm build

@netlify
Copy link

netlify bot commented Mar 23, 2026

Deploy Preview for viteplus-preview ready!

Name Link
🔨 Latest commit b1d23ec
🔍 Latest deploy log https://app.netlify.com/projects/viteplus-preview/deploys/69c15d9214a8ca00072cb100
😎 Deploy Preview https://deploy-preview-1116--viteplus-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@yash27-lab
Copy link
Author

Opened a PR for this:
#1116

This adds a manual package-manager install path for vp, plus PATH / pnpm setup / vp env setup / vp env off notes and matching upgrade commands.

I also verified the npm/pnpm install and upgrade commands in isolated temp environments and ran the docs build successfully.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d1d31c4adc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".


- It does not modify your shell profile for you.
- It does not automatically create the `node`, `npm`, and `npx` shims in `VITE_PLUS_HOME/bin`.
- If you want Vite+ to manage those shims after installing, run `vp env setup`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Remove the vp env setup follow-up for package-manager installs

Following this bullet after npm install -g vite-plus/pnpm add -g vite-plus creates ~/.vite-plus/bin/vp and the node/npm/npx shims via setup_vp_wrapper()/create_unix_shim() in crates/vite_global_cli/src/commands/env/setup.rs, and all of them point at ../current/bin/vp. A package-manager install never creates VITE_PLUS_HOME/current; that only happens in the installer/upgrade flow (packages/cli/install.sh and swap_current_link() in crates/vite_global_cli/src/commands/upgrade/install.rs). If a user follows this advice and then adds ~/.vite-plus/bin to PATH, vp becomes a broken shim.

Useful? React with 👍 / 👎.

Comment on lines +41 to +44
This installation path is more manual than the install script:

- It does not modify your shell profile for you.
- It does not automatically create the `node`, `npm`, and `npx` shims in `VITE_PLUS_HOME/bin`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Warn that vp implode won't uninstall npm/pnpm installs

Now that this section documents npm/pnpm as a supported global install path, the caveats also need to say that vp implode does not remove that installation. execute() in crates/vite_global_cli/src/commands/implode.rs only deletes VITE_PLUS_HOME and cleans shell-profile snippets, so an npm/pnpm-owned vp binary remains on PATH until the user runs the matching package-manager uninstall command. Without that warning, the cleanup guidance on this page becomes incorrect for users who choose the new install method.

Useful? React with 👍 / 👎.


### Install with npm or pnpm

If you prefer not to pipe a remote script into your shell, you can install the published `vite-plus` package globally with a package manager instead:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the vp cli from vite-plus's package we call it Local CLI. It is not recommended to install this Local CLI globally through a package manager, as its features differ from those of the Global CLI, such as the lack of node runtime manager(e.g.: vp env command is missing) and package manager functionalities.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, that makes sense.

I misunderstood the published vite-plus package as a supported global installation path for the full vp CLI. I’ll avoid documenting it that way.

Would you prefer this PR to be reshaped to clarify that:

  • the install script is the supported way to install the global vp CLI
  • the published vite-plus package is the project-local CLI and should not be installed globally

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants