Skip to content

docs(upgrade): document aliased package update steps #1266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
graphite-app merged 1 commit into from
Apr 2, 2026
+21 −0
Merged

docs(upgrade): document aliased package update steps #1266

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/guide/upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,24 @@ vp update vite-plus
```

You can also use `vp add vite-plus@latest` if you want to move the dependency explicitly to the latest version.

### Updating Aliased Packages

Vite+ sets up npm aliases for its core packages during installation:

- `vite` is aliased to `npm:@voidzero-dev/vite-plus-core@latest`
- `vitest` is aliased to `npm:@voidzero-dev/vite-plus-test@latest`

`vp update vite-plus` does not re-resolve these aliases in the lockfile. To fully upgrade, update them separately:

```bash
vp update @voidzero-dev/vite-plus-core @voidzero-dev/vite-plus-test
```

Or update everything at once:

```bash
vp update vite-plus @voidzero-dev/vite-plus-core @voidzero-dev/vite-plus-test
```

You can verify with `vp outdated` that no Vite+ packages remain outdated.
Loading