Migrate or align frontend package and monorepo repositories to Vite+, including CI, tests, packaging, hooks, and Vite+ 0.2.x Vitest-wrapper cleanup.
86
—
Does it follow best practices?
Impact
86%
1.38xAverage score across 7 eval scenarios
Passed
No findings from the security scan
No parallel vitest.config.ts
100%
100%
No .oxlintrc* files
100%
100%
No parallel tsdown.config.ts
100%
100%
typeAware enabled
0%
100%
typeCheck enabled
0%
100%
baseUrl incompatibility addressed
0%
100%
Staged config in vite.config.ts
0%
100%
No Husky or lint-staged config
40%
100%
defineConfig from vite-plus
0%
100%
vp migrate referenced
0%
0%
vite-plus/test imports
25%
100%
vp test in scripts
100%
80%
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
0%
30%
Coverage dependency kept aligned
100%
100%
vp run -t for build chain
0%
0%
No pnpm --filter ellipsis
100%
100%
Library build seed in dev script
83%
100%
--parallel flag in dev
70%
80%
No external task-runner invented
100%
100%
Library watch uses vp pack --watch
20%
100%
Build-first for demo app
100%
100%
Single workspace-wide hook config
25%
100%
No direct package manager for tasks owned by Vite+
0%
30%
vp pack for library
100%
100%
Pack concurrency bounded
0%
0%
Pack config in vite.config.ts
100%
100%
No parallel tsdown config
100%
100%
vp staged for hooks
100%
100%
No Husky or lint-staged
100%
100%
pnpm override for Vite core
100%
0%
No direct pnpm/npm/yarn commands
50%
100%
Docs updated with new commands
30%
40%
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%
Includes setup-vp template
66%
46%
Extends setup-vp job
100%
100%
Node remains job-owned
100%
100%
GitLab cache retained
100%
100%
No manual package-manager bootstrap
100%
100%
No duplicate install
100%
100%
Uses stock verify commands
13%
73%
Template refs aligned
100%
100%
Responsibility boundary documented
90%
100%
No global CLI dependency
100%
100%
Pinned package manager bootstrap
100%
87%
vp migrate for local stack
100%
100%
Core alias verified
46%
53%
Removed obsolete test wrapper
66%
66%
vp outdated for verification
0%
100%
Direct Vitest usage classified
37%
25%
Local CLI version in validation
100%
100%
Full validation sequence
100%
100%
Build validation included
0%
100%
No direct package manager for local Vite+ stack
100%
100%
Table of Contents