What problem does it solve?
Setting up Vite+ in a monorepo involves subtle decisions about task graphs, cache behavior, packaging boundaries, and CI cache keys, and misconfiguration leads to broken dependency ordering, cache misses, and slow builds.
Core Features & Use Cases
- Task Graph Configuration: Define
run.tasks with proper dependsOn edges, workspace selection, and package#task synthetic dependencies instead of serial shell pipelines.
- Cache Diagnosis and CI Setup: Prove local Vite Task cache hits, then configure GitHub Actions restore/save of
node_modules/.vite/task-cache with correct key strategy.
- Pack and Migration Guidance: Configure
vp pack for library builds using named configs, --filter, and shared packaging defaults from build/pack.ts.
- Use Case: A sandbox build consumes workspace packages plus generated CDN HTML files; the Skill produces a build task declaring both workspace edges and the
@videojs/html#build:cdn artifact dependency, verified with a clean run followed by a cache-hit second run.
Quick Start
Configure the Vite+ build task graph and caching for this monorepo and verify the second run hits the cache.