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

Passed

No known issues

This version of the tile failed moderation
Failed moderation (intent review) in tile.json: This is a potential supply chain attack via typosquatting/dependency confusion. The package name 'uinaf/viteplus' mimics the popular 'Vite' ecosystem (vite-plus, voidzero-dev). It's designed as an AI agent tile/skill that instructs AI coding assistants to modify package scripts, CI configurations, and packaging commands in repositories - effectively a prompt injection attack. The skill directs AI agents to replace legitimate tooling with attacker-controlled alternatives ('vp', 'voidzero-dev/setup-vp', 'vite-plus/test'), which could introduce malicious dependencies across many repositories when an AI agent follows these instructions.
Overview
Quality
Evals
Security
Files

known-issues.mdreferences/

Known Issues (alpha)

VitePlus is still in alpha. These are real, recent caveats observed against the upstream issue tracker. Surface them only if the repo actually hits them — do not preemptively work around something a stock setup is fine with. Re-check this list against the issue tracker when adopting a newer release.

Hook runner compatibility

vp opens /dev/tty directly, which causes it to hang when spawned by non-interactive hook tools such as lefthook.

  • Prefer the stock vp config / .vite-hooks path.
  • If the repo has a reason to use lefthook or similar, run the hook command through vp run --silent and verify it returns under load before merging.
  • Tracking: voidzero-dev/vite-plus#1396.

vp check --fix on a single file

Single-file invocations can emit spurious TS2591 errors for node:* imports while a full-project vp check --fix passes.

  • If staged runs per-file vp check --fix, fall back to a vp check --fix over the staged set, or scope staged to non-TS globs until upstream lands a fix.
  • Tracking: voidzero-dev/vite-plus#1443.

TanStack Start / SSR instanceof failures

Some package managers (notably bun, sometimes npm) install two physical copies of @voidzero-dev/vite-plus-core — once via the vite alias and once via vite-plus's direct dependency — which breaks SSR isRunnableDevEnvironment() checks.

  • If SSR fails after migration, run vp dedupe and confirm only one @voidzero-dev/vite-plus-core exists under node_modules.
  • Tracking: voidzero-dev/vite-plus#1391.

Cloudflare Workers tests

@cloudflare/vitest-pool-workers currently fails under vp test (Cannot read properties of undefined (reading 'config')) while plain vitest run passes.

@vitest/coverage-v8 mixed-version warnings

Adding @vitest/coverage-v8 to a VitePlus project can still produce a mixed-version warning during vp test run --coverage, even in a fresh stock scaffold.

  • Treat as a known VitePlus limitation. Verify the same warning reproduces in a fresh stock scaffold before calling it a repo bug.

references

bootstrap.md

ci-cd.md

commands.md

known-issues.md

monorepos.md

packages.md

testing.md

SKILL.md

tile.json