Cache never hits for vp pack / vp build tasks (modified their inputs)

[alvarosabu]

Description

I followed the steps in this video to set up VitePlus in our monorepo (TresJS) and everything works great — builds, lint, etc. However, I can't get --cache to work for vp pack / vp build tasks.

Steps to reproduce

1. Monorepo with multiple library packages, each with "build": "vp pack" in package.json
2. Run vp run -r build --cache — first run completes, all tasks show cache miss (expected)
3. Run vp run -r build --cache again — 0% cache hit rate

What happens

Every task reports "Not cached: read and wrote ..." pointing to two types of files:

1. dist/ output files — e.g. packages/core/dist/tres.d.ts
2. .vite-temp/ config compilation artifacts — e.g. packages/core/node_modules/.vite-temp/vite.config.ts.timestamp-*.mjs

Since vp pack reads and writes to dist/, the auto file tracker sees the task modifying its own inputs, so cache can never hit.

[1] @tresjs/eslint-config#build: ~/packages/eslint-config$ vp pack ✓
    → Not cached: read and wrote 'packages/eslint-config/dist/index.cjs'

[2] @tresjs/core#build: ~/packages/core$ vp pack ✓
    → Not cached: read and wrote 'packages/core/node_modules/.vite-temp/vite.config.ts.timestamp-*.mjs'

Workaround found

We got cache working by:

1. Moving the build script from package.json to run.tasks in vite.config.ts with input exclusions:

export default defineConfig({
  run: {
    tasks: {
      build: {
        command: 'vp pack',
        input: [{ auto: true }, '!dist/**', '!**/node_modules/.vite-temp/**'],
      },
    },
  },
})

2. Removing the "build" script from package.json (VitePlus errors if both exist with the same name)

After this, cache hits work on subsequent runs.

Question

Is this the expected setup? It feels like vp pack and vp build should either:

• Automatically exclude their own output directories (dist/) from cache input tracking
• Or exclude .vite-temp/ compilation artifacts by default

Since these are VitePlus's own commands, it seems like the cache should work out of the box without needing manual input exclusions. Maybe we're missing a configuration step?

Environment

• vite-plus: 0.1.14
• Node: v22
• pnpm: 10.20.0
• macOS Darwin 25.3.0

[fengmk2]

Yes, there is a bug in the latest released version of the vp pack command, which has been fixed in #1096.
You can try upgrading to the vite-plus@alpha test version to verify.
Also, the —cache parameter needs to be added before {taskName}, such as vp run -r —cache build.

[alvarosabu]

Hi @fengmk2 thanks for reaching out so fast! So I upgrade to the alpha test version and ran vp run -r --cache build in the root of the monorepo and also vp run --cache core#build for an individual package pack and both missed the cache:

---
vp run: 0/16 cache hit (0%). @tresjs/monorepo-cli#build (and 15 more) not cached because they modified their inputs. (Run `vp run --last-details` for full details)

[fengmk2]

@alvarosabu Could you provide a reproduce repo URL? I'll try to debug it.

[fengmk2]

@alvarosabu I think I've found the problem, let me fix it.

[alvarosabu]

Hey @fengmk2 sorry I didn't provide a repo, was away the rest of the weekend. I think it was reproducible on the starter via vp create but if not, I can publish the branch on tresjs with the migration

[fengmk2]

@alvarosabu No worries, I’ve already found a way to reproduce it. I’ve identified and fixed it in a repo I created. If you can provide a branch of the tresjs repo, that would be even better so I can test it on tresjs ahead of time.

[fengmk2]

@alvarosabu please take a try at vite-plus@0.1.15, I think it will cache well by default.

[alvarosabu]

Hi @fengmk2 I just tested it on the Tresjs branch chore/viteplus-migration

Most of the packages I would expect to be cached where cached 🎉, with the execption of @tresjs/leches which I think it might be using autoimports maybe?

Maybe worth adding some folders to "cacheignore" kind of config? Or maybe a property to exclude certain files to invalidate the cache

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Vite+ Task Runner • Execution Summary
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Statistics:   16 tasks • 6 cache hits • 10 cache misses
Performance:  37% cache hit rate, 15.38s saved in total

Task Details:
────────────────────────────────────────────────
  [1] @tresjs/monorepo-cli#build: ~/tools/monocubo$ vp pack ✓
      → Cache hit - output replayed - 127ms saved
  ·······················································
  [2] @tresjs/eslint-config#build: ~/packages/eslint-config$ vp pack ✓
      → Cache hit - output replayed - 795ms saved
  ·······················································
  [3] @tresjs/core#build: ~/packages/core$ vp pack ✓
      → Cache hit - output replayed - 2.13s saved
  ·······················································
  [4] @tresjs/rapier#build: ~/packages/rapier$ vp pack ✓
      → Cache hit - output replayed - 1.98s saved
  ·······················································
  [5] @tresjs/cientos#build: ~/packages/cientos$ vp pack ✓
      → Cache hit - output replayed - 7.63s saved
  ·······················································
  [6] @tresjs/leches#build: ~/packages/leches$ vp build ✓
      → Not cached: read and wrote 'packages/leches/node_modules/.vue-global-types/vue_3.5_false.d.ts'
  ·······················································
  [7] @tresjs/post-processing#build: ~/packages/postprocessing$ vp pack ✓
      → Cache hit - output replayed - 2.72s saved
  ·······················································
  [8] @tresjs/nuxt#build: ~/packages/nuxt$ pnpm run module:build ✓
      → Not cached: read and wrote 'packages/nuxt/.nuxt/pages.mjs'
  ·······················································
  [9] @tresjs/nuxt#build: ~/packages/nuxt$ pnpm run client:build ✓
      → Not cached: read and wrote 'packages/nuxt/client/.nuxt/ui/marquee.ts'
  ·······················································
  [10] playground#build: ~/apps/playground$ vp build ✓
      → Not cached: read and wrote 'apps/playground/auto-imports.d.ts'
  ·······················································
  [11] postprocessing-docs-vitepress#build: ~/apps/postprocessing-docs-vitepress$ vitepress build ✓
      → Not cached: read and wrote 'apps/postprocessing-docs-vitepress/.vitepress/.temp/lens-distortion/room-map.png'
  ·······················································
  [12] docs-boilerplate#build: ~/apps/docs-boilerplate$ nuxt build ✓
      → Not cached: read and wrote 'apps/docs-boilerplate/.output/server/node_modules/reka-ui/dist/composables/useWindowSplitterPanelGroupBehavior.js'
  ·······················································
  [13] playground-nuxt#build: ~/apps/playground-nuxt$ nuxi build ✓
      → Not cached: read and wrote 'apps/playground-nuxt/.output/server/node_modules/three-stdlib/libs/mmdparser.js'
  ·······················································
  [14] tresjs-docs#build: ~/apps/docs$ nuxt build ✓
      → Not cached: read and wrote 'apps/docs/node_modules/.cache/nuxt/.nuxt/dist/server/_nuxt/Steps.d.vue-BTDBFo2Y.js.map.json'
  ·······················································
  [15] cientos-docs#build: ~/apps/cientos-docs$ nuxt build ✓
      → Not cached: read and wrote 'apps/cientos-docs/.output/server/node_modules/reka-ui/dist/Slider/SliderRoot.js'
  ·······················································
  [16] tresjs-lab#build: ~/apps/lab$ nuxt build ✓
      → Not cached: read and wrote 'apps/lab/.output/server/node_modules/three-stdlib/cameras/CinematicCamera.js'

[fengmk2]

@alvarosabu You can refer to the https://viteplus.dev/config/run#input configuration to add patterns like .vitepress/.temp to the exclude files rule: !.vitepress/.temp/**