uinaf/viteplus
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.
94
2.63x
Quality
94%
Does it follow best practices?
Impact
95%
2.63xAverage score across 3 eval scenarios
Securityby
Passed
No known issues
monorepos.mdreferences/
Monorepos
Use this reference for workspace repos adopting VitePlus.
Defaults
- Move workspace scripts, test surface, and CI together instead of partially migrating leaf packages.
- Keep workspace package-manager conventions and cache boundaries unless VitePlus replaces them cleanly.
- Leaf packages and apps should still prefer
vp check,vp test, andvp packwhere VitePlus is the real tool owner. - Use
vp run @pkg/task,vp run -r,vp run -t, andvp run --filterinstead of inventing custom workspace task wrappers when VitePlus already owns the task graph.
Guardrails
- Do not force VitePlus onto non-frontend or non-Node packages.
- Keep workspace-specific caching and dependency ordering rules if VitePlus does not fully cover them yet.
- Verify the important leaf packages still build and test after the migration.