Migrate or align frontend repositories to the stock VitePlus workflow. Use when standardizing package or monorepo repos around `vp`, `voidzero-dev/setup-vp`, `vite-plus/test`, and VitePlus-native CI, test, and packaging flows, including updating scripts, test config, CI setup, and packaging commands.
98
100%
Does it follow best practices?
Impact
97%
1.73xAverage score across 6 eval scenarios
Passed
No known issues
vp pack for library
0%
100%
Pack config in vite.config.ts
100%
100%
No parallel tsdown config
100%
100%
vp staged for hooks
0%
100%
No Husky or lint-staged
0%
100%
pnpm overrides for vite and vitest
0%
100%
No direct pnpm/npm/yarn commands
100%
100%
Docs updated with new commands
0%
100%
Uses setup-vp action
0%
100%
No redundant vp env step
100%
100%
Uses vp install
0%
100%
Uses vp check and vp test
0%
100%
vp run for custom scripts
0%
100%
No direct package manager commands
0%
100%
Release steps preserved
100%
100%
Release workflow file retained
100%
100%
Output includes workflow files
100%
100%
vite-plus/test imports
100%
100%
vp test in scripts
100%
66%
No invented vp subcommands
100%
100%
Watch script uses vp test watch
100%
100%
Coverage script uses vp test run --coverage
100%
100%
Coverage migrated together
100%
100%
No direct package manager test call
100%
100%
Coverage-v8 caveat documented
100%
100%
No parallel vitest.config.ts
100%
100%
No .oxlintrc* files
100%
100%
No parallel tsdown.config.ts
100%
100%
typeAware enabled
100%
100%
typeCheck enabled
100%
100%
baseUrl incompatibility addressed
100%
100%
Staged config in vite.config.ts
100%
100%
No Husky or lint-staged config
100%
100%
defineConfig from vite-plus
100%
100%
vp migrate referenced
0%
0%
vp run -t for build chain
0%
100%
No pnpm --filter ellipsis
100%
100%
Library build seed in dev script
0%
100%
--parallel flag in dev
40%
100%
No external task-runner invented
100%
100%
Library watch uses vp pack --watch
0%
100%
Build-first for demo app
20%
100%
Single workspace-wide hook config
25%
100%
No direct package manager for VitePlus-owned tasks
0%
40%
vp upgrade for global CLI
16%
100%
Global before local
87%
100%
vp update vite-plus
0%
100%
Explicit core alias update
60%
100%
Explicit test alias update
60%
100%
vp outdated for verification
0%
100%
vp env current in validation
0%
100%
Full validation sequence
40%
100%
Build validation included
0%
100%
No direct package manager for VitePlus packages
0%
100%
Table of Contents