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.

2.63x

Quality

94%

Does it follow best practices?

Impact

95%

2.63x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

CI/CD

Name: uinaf/viteplus
Rating: 94.2 (1 reviews)
Author: uinaf

Use this reference before changing GitHub Actions or release automation.

Prefer the documented VitePlus setup:

- uses: voidzero-dev/setup-vp@v1
- run: vp env
- run: vp install
- run: vp check && vp test

Defaults

Prefer voidzero-dev/setup-vp@v1 over hand-rolled Node/Corepack bootstrapping unless the repo has a proven exception.
Prefer vp install over separate package-manager bootstrap logic when VitePlus is the tool owner.
Prefer vp config when the repo wants stock hooks or agent integration instead of hand-rolled hook setup.
Prefer one repo-local verify entrypoint if CI needs extra repo-specific commands.
Keep release orchestration in GitHub Actions when the repo has npm, GitHub Release, binary, or Homebrew automation that goes beyond stock VitePlus.

Guardrails

Prefer vp run <script> when CI needs a repo-specific script that VitePlus does not replace.
Do not delete release-only steps just to make the workflow look more stock.
Keep packaging and publish steps that VitePlus does not own.