#1992 (comment)
Problem
Today, Vite Task cache applies when a build is run as a task, for example vpr build or vp run build. A user can get cache hits from that task path, but direct built-in commands like vp build and vp pack do not use the task cache.
That makes the behavior hard to explain. vpr build can hit cache while vp build always runs, even though both may execute the same build command.
Possible direction
Add a config option that lets projects enable caching for built-in vp build and vp pack commands. This would make the first-party command path and the task-runner path behave more consistently.
#1992 (comment)
Problem
Today, Vite Task cache applies when a build is run as a task, for example
vpr buildorvp run build. A user can get cache hits from that task path, but direct built-in commands likevp buildandvp packdo not use the task cache.That makes the behavior hard to explain.
vpr buildcan hit cache whilevp buildalways runs, even though both may execute the same build command.Possible direction
Add a config option that lets projects enable caching for built-in
vp buildandvp packcommands. This would make the first-party command path and the task-runner path behave more consistently.