Repository navigation
Support Vite Task GitHub Actions cache in setup-vp #2013
Description
Problem
The GitHub Actions cache guide currently asks users to wire Vite Task cache manually with actions/cache restore and save steps.
That makes every project choose its own cache path and key shape for node_modules/.vite/task-cache. It is easy to get wrong, and users have to repeat the same workflow config in each repository.
Possible direction
Add first-class Vite Task cache support to voidzero-dev/setup-vp.
setup-vp could provide a good default path and cache key for Vite Task, while still allowing projects to opt in and override defaults when needed. This should stay separate from package-manager dependency caching.
Context
Raised during review of #1992. The docs can keep the manual workflow for now, but setup support would make the common case simpler.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Activity
KTrain5169 commentedon Jul 20, 2026
Would it be alright if I looked into implementing this?
KTrain5169 commentedon Aug 13, 2026
wrote an implementation and PR'd it to
voidzero-dev/setup-vpcderinbogaz commentedon Sep 7, 2026
Disclosure: I work on Runnerhut. For setup-vp#126, I would include a consumer-level test where dependency caching is disabled but task caching is enabled, and the reverse. That would prove the two controls remain independent. Also test a configured cache path in a subdirectory and a source/env change after an outer GitHub cache hit. The useful measurement is avoided task execution, not just successful archive restoration; a runner change should be evaluated separately from that gain.