From 8f4e7616105f470d1b523f1d47d1f56e0cb8959e Mon Sep 17 00:00:00 2001 From: JongKyung Lee Date: Thu, 8 Oct 2026 16:23:04 +0900 Subject: [PATCH] docs: clarify version requirements for env uninstall --- docs/guide/env.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/env.md b/docs/guide/env.md index e72c43f583..0e6fb912c8 100644 --- a/docs/guide/env.md +++ b/docs/guide/env.md @@ -179,7 +179,7 @@ In CI, `vp env use` can run without shell initialization. It writes a temporary - `vp env unpin` removes both effective pins by default; append a selector to remove one. Lower-priority declarations are not deleted. - `vp env use` activates the complete project environment. Explicit specs override selected components; `--unset` clears both unless scoped. - `vp env install` installs the complete resolved environment, a selected component, or explicit specs. -- `vp env uninstall` removes explicit exact Node.js or qualified package-manager versions. +- `vp env uninstall` removes the Node.js version resolved from an explicit version or selector, such as `22` or `lts`. Package managers require a qualified exact version, such as `pnpm@10.18.0`. - `vp env clean` removes unused installs. Use `clean node`, `clean pm`, or a concrete manager. Current and configured-default versions are preserved. - `vp env exec` runs a command in the resolved environment. Use `--node` and `--package-manager`; `--npm` is an alias for `--package-manager npm@…`. - `vp node` uses the resolved Node.js runtime and exposes the selected package-manager path to child processes.