Skip to content

chore: upgrade Vite+ to 1.6 and apply vp migrate - #781

Merged
cpojer merged 3 commits into
mainfrom
chore/vp-upgrade
Nov 11, 2026
Merged

cpojer merged 3 commits into
mainfrom
chore/vp-upgrade

Conversation

@kossnocorp

Copy link
Copy Markdown
Contributor

I had an error running vp run build on a fresh checkout:

$ vp run build:all
error: Failed to plan tasks from `vp run build` in task build:all
* Failed to plan tasks from `vp run --filter './packages/**' --parallel build` in task build
* Invalid vite task command: vp with args ["pack"] under cwd /Users/skoss/code/voidzero/voidzero-dev/void/packages/create-void
* Failed to resolve pack command: GenericFailure, Expected @voidzero-dev/vite-plus-core@1.6.0, but found @voidzero-dev/vite-plus-core@1.5.0 at /Users/skoss/code/voidzero/voidzero-dev/void/node_modules/.pnpm/@voidzero-dev+vite-plus-core@1.5.0_@types+node@26.6.6_esbuild@0.28.2_jiti@2.7.0_sass-em_1594fd50e3acc8a93202304e36c63c1d/node_modules/@voidzero-dev/vite-plus-core/package.json. Run `vp migrate` to align the Vite alias, then run `vp install`.

The problem was that I had a newer Vite+ version (tested with 1.5.1 and 1.6.0).

So I applied vp migrate.

@socket-security

socket-security Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​voidzero-dev/​vite-plus-core@​1.5.0 ⏵ 1.6.098 +110077 +199 +2100
Updatedvite-plus@​1.5.0 ⏵ 1.6.098 +1100100100 +2100

View full report

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://chore-vp-upgrade-void-cloud.voidzero-docs.workers.dev (commit 8267a01)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://456dacc5-void-cloud.voidzero-docs.workers.dev 8267a01 2026-11-11T08:46:36.798Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://8ee128d9-void-cloud.voidzero-docs.workers.dev adf1fa2 2026-11-11T08:26:08.983Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://c886f964-void-cloud.voidzero-docs.workers.dev 6471f94 2026-11-11T06:35:08.743Z Visit the dashboard ↗
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://68f353b2-void-cloud.voidzero-docs.workers.dev cfd33aa 2026-11-11T06:26:50.603Z Visit the dashboard ↗

cpojer pushed a commit that referenced this pull request Nov 11, 2026
…orts (#782)

## Summary

`vp lint` and `vp check` did not report imports from `vitest`. Vite+
reports them with the `vite-plus/prefer-vite-plus-imports` rule from its
`vite-plus/oxlint-plugin` JS plugin. This rule runs only when the `lint`
block lists both the plugin and the rule. `vp create` and `vp migrate`
add them only when a project has no `lint` block yet. Void had a `lint`
block before Vite+ added the rule, so the rule never ran here.

## Changes

- `vite.config.ts`: add the `vite-plus/oxlint-plugin` JS plugin and set
`vite-plus/prefer-vite-plus-imports` to `error`.
- Seven platform test files in `platform/packages/{api,dashboard}/test`:
import from `vite-plus/test` instead of `vitest`.

## Behavior

- A new import from `vitest` or `@vitest/browser*` now fails `vp lint`,
`vp check`, and the staged-files hook.
- `vp check --fix` rewrites the import to the matching `vite-plus/test*`
path.
- `declare module 'vitest'` augmentations stay valid. The rule does not
report them.
- Lint time on the full repository stays about the same: 1.2–1.7 s
before, about 1.5 s after.

## Relation to #781

#781 makes the same seven import changes as part of the Vite+ 1.6
upgrade. The edits are identical, so the two PRs do not conflict. This
PR does not remove the `vitest` devDependency from
`platform/package.json` or the catalog entry. #781 removes them together
with the upgrade.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
I had an error running `vp run build` on a fresh checkout:

```
$ vp run build:all
error: Failed to plan tasks from `vp run build` in task build:all
* Failed to plan tasks from `vp run --filter './packages/**' --parallel build` in task build
* Invalid vite task command: vp with args ["pack"] under cwd /Users/skoss/code/voidzero/voidzero-dev/void/packages/create-void
* Failed to resolve pack command: GenericFailure, Expected @voidzero-dev/vite-plus-core@1.6.0, but found @voidzero-dev/vite-plus-core@1.5.0 at /Users/skoss/code/voidzero/voidzero-dev/void/node_modules/.pnpm/@voidzero-dev+vite-plus-core@1.5.0_@types+node@26.6.6_esbuild@0.28.2_jiti@2.7.0_sass-em_1594fd50e3acc8a93202304e36c63c1d/node_modules/@voidzero-dev/vite-plus-core/package.json. Run `vp migrate` to align the Vite alias, then run `vp install`.
```

The problem was that I had a newer Vite+ version (tested with 1.5.1 and
1.6.0).

So I applied `vp migrate`.
@kossnocorp
kossnocorp marked this pull request as ready for review November 11, 2026 08:45
@kossnocorp
kossnocorp requested a review from a team as a code owner November 11, 2026 08:45

@cpojer cpojer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thank you!

@cpojer
cpojer merged commit cd9de09 into main Nov 11, 2026
18 checks passed
@cpojer
cpojer deleted the chore/vp-upgrade branch November 11, 2026 08:50
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