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
{
"context": "Tests whether the agent correctly configures a TypeScript library for packaging using Vite+ conventions: using vp pack with bounded concurrency when required, placing pack config in vite.config.ts, using vp staged for hooks, adding the required Vite core override, and updating contributor docs.",
"type": "weighted_checklist",
"checklist": [
{
"name": "vp pack for library",
"description": "The `build` or `pack` script in package.json uses `vp pack` and NOT `vp build` (since this is a library, not a web application)",
"max_score": 10
},
{
"name": "Pack concurrency bounded",
"description": "The packaging command uses `vp pack --concurrency 2` so the stated memory-constrained CI workers run at most two Rolldown builds in parallel",
"max_score": 5
},
{
"name": "Pack config in vite.config.ts",
"description": "Library packaging configuration (entry points, formats, output options) is placed inside `vite.config.ts` rather than in a separate config file",
"max_score": 15
},
{
"name": "No parallel tsdown config",
"description": "The output does NOT include a `tsdown.config.ts` or `tsdown.config.js` file as a parallel packaging config",
"max_score": 10
},
{
"name": "vp staged for hooks",
"description": "Pre-commit hook configuration uses `staged` inside `vite.config.ts` (the `defineConfig` `staged` property) rather than a separate `.husky/` directory, `lint-staged` config, or shell-hook wiring",
"max_score": 15
},
{
"name": "No Husky or lint-staged",
"description": "The output does NOT add `husky`, `lint-staged`, or `.husky/` configuration for pre-commit hooks",
"max_score": 10
},
{
"name": "pnpm override for Vite core",
"description": "The package-manager override/resolution/catalog keeps `vite` mapped to the matching `npm:@voidzero-dev/vite-plus-core@<version>`; it does not add the removed `@voidzero-dev/vite-plus-test` wrapper for node-mode-only tests",
"max_score": 15
},
{
"name": "No direct pnpm/npm/yarn commands",
"description": "Scripts in package.json do NOT use `pnpm run`, `npm run`, or `yarn run` for any command that Vite+ replaces (install, test, build)",
"max_score": 10
},
{
"name": "Docs updated with new commands",
"description": "The README or CONTRIBUTING file uses `pnpm install --frozen-lockfile` for bootstrap and the repository-local Vite+ CLI (`pnpm exec vp pack`) for interactive build instructions",
"max_score": 10
}
]
}