CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

98

1.73x
Quality

100%

Does it follow best practices?

Impact

97%

1.73x

Average score across 6 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

packages.mdreferences/

Packages

Use this reference for standalone package repos adopting VitePlus.

Defaults

  • Prefer vp pack for libraries and standalone executables (pack.exe = true for native binaries).
  • Prefer vp check and vp test as the default verify surface.
  • Keep pack config in vite.config.ts instead of maintaining a parallel tsdown.config.ts. After migrating, delete the standalone tsdown.config.ts.

Aliased Dependencies

  • pnpm repos should add overrides for VitePlus-wrapped vite and vitest:

    # pnpm-workspace.yaml
    overrides:
      vite: npm:@voidzero-dev/vite-plus-core@latest
      vitest: npm:@voidzero-dev/vite-plus-test@latest
  • npm projects use overrides in package.json; Yarn projects use resolutions.

Notes

  • vp pack --watch is the watch-mode equivalent for libraries; pair it with vp run -r --parallel dev in monorepos that consume the library via dist/.
  • Keep SDK, codegen, or bootstrap steps that VitePlus does not replace.
  • Update docs when install, test, or packaging commands change.

SKILL.md

tile.json