configure-vite-plus

Configure Vite+ task graphs, caching, packaging, and CI workflows.

931|91|Updated Aug 13, 2025
One-click install
npx skills add https://github.com/videojs/v10 --skill configure-vite-plus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-vite-plus
Source: https://github.com/videojs/v10/tree/main/.agents/skills/configure-vite-plus
Command: npx skills add https://github.com/videojs/v10 --skill configure-vite-plus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about configure-vite-plus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Vite+ task dependencies in a monorepo?

Define ordering in run.tasks within vite.config.ts using dependsOn entries. Use { task: 'build', from: ['dependencies', 'devDependencies'] } for declared workspace edges and package#task syntax for synthetic cross-package dependencies like generated assets.

How do I set up Vite+ caching in GitHub Actions?

Install dependencies first, restore node_modules/.vite/task-cache, run the same vp run tasks used locally, then save only after success. Keep source and lockfile hashes out of the Actions cache key because Vite Task fingerprints task inputs itself.

What is the difference between vp build, vp pack, and vp run?

vp build handles application builds, vp pack handles library packaging via tsdown settings in the pack config block, and vp run orchestrates configured tasks with caching. Only vp run uses Vite Task caching.

Why is my Vite+ task cache not hitting on the second run?

Cache misses usually come from unstable inputs such as generators rewriting unchanged files or missing input/output declarations. Run the exact task twice locally, inspect observed reads and writes, then add input, output, env, or untrackedEnv entries only from observed misses.

When should I use --parallel with Vite+ tasks?

Reserve --parallel for independent persistent tasks such as development servers, since it deliberately ignores task dependencies. Never lower concurrency or use it to work around missing dependency edges in the task graph.