Issues

Issues

• Add task configuration to a package.json script without a second name

  voidzero-dev/vite-task#995 · opened on Nov 12, 2026

• A run that restores cache hits and never executes a miss, to prime a checkout

  voidzero-dev/vite-task#994 · opened on Nov 12, 2026

• When the local and remote entries both miss, the miss reason describes only the local one

  voidzero-dev/vite-task#993 · opened on Nov 12, 2026

• Gitignored entries count in directory listings, so a used checkout misses the entries a fresh checkout recorded

  voidzero-dev/vite-task#992 · opened on Nov 12, 2026

• fspy changes a shebang script's process name under input: [{ auto: true }]

  voidzero-dev/vite-task#954 · opened on Nov 7, 2026
  1

• A dry run marks a step unknown behind a cached prerequisite that restores outputs, though the restore gives it the exact files it recorded

  voidzero-dev/vite-task#938 · opened on Nov 5, 2026

• A miss on a fresh checkout runs tsc --incremental with no build info, though the step's entry archived it

  voidzero-dev/vite-task#936 · opened on Nov 5, 2026

• ☂️ New Linux file tracking backend

  Feature

  voidzero-dev/vite-task#932 · opened on Nov 4, 2026

• Reuse remote cache entries across main and pull requests, safely

  Task

  voidzero-dev/vite-task#931 · opened on Nov 4, 2026

• ☂️ Release remote caching

  Feature

  voidzero-dev/vite-task#930 · opened on Nov 4, 2026

• ☂️ Cache tools that maintain their own cache

  Feature

  voidzero-dev/vite-task#929 · opened on Nov 4, 2026

• Node.js module compile cache support

  voidzero-dev/vite-task#928 · opened on Nov 3, 2026

• Remote cache keys always include the OS and architecture, so a task whose outputs are the same on every platform can't share entries between macOS and Linux

  voidzero-dev/vite-task#926 · opened on Nov 2, 2026

• A task config has no place for settings another tool reads, so keeping them beside the task takes a patch to Vite+

  voidzero-dev/vite-task#925 · opened on Nov 2, 2026

• A remote cache hit is never stored back, so a server that shares entries across endpoints can't keep each endpoint's own entries current

  voidzero-dev/vite-task#924 · opened on Nov 2, 2026

• vp run: a live log of run events, so a failure can be acted on while the run continues (today nothing names a failure until the run ends)

  voidzero-dev/vite-task#923 · opened on Nov 2, 2026

• A negative input pattern can't be narrowed, so keeping one folder under node_modules tracked takes a sibling-name glob

  voidzero-dev/vite-task#921 · opened on Oct 30, 2026
  1

• On macOS, files cp writes are not recorded as outputs, although fspy swaps cp for its bundled coreutils

  voidzero-dev/vite-task#910 · opened on Oct 29, 2026
  1

• Export OpenTelemetry client spans for the native remote cache

  voidzero-dev/vite-task#906 · opened on Oct 29, 2026

• An input edited while a cached task runs is fingerprinted after the run, so the next run replays output built from the old content

  voidzero-dev/vite-task#905 · opened on Oct 29, 2026

• cache.output: opt-in exact restore, so a hit removes files the cached run did not write

  voidzero-dev/vite-task#904 · opened on Oct 29, 2026

• A git worktree never replays a checkout's cache entry for a task that lists the workspace root

  voidzero-dev/vite-task#902 · opened on Oct 28, 2026
  1

• A cache hit rewrites every output file, unchanged ones included, so watchers see all outputs change

  voidzero-dev/vite-task#900 · opened on Oct 28, 2026

• A task output archive larger than the remote cache server's request limit can never be stored

  voidzero-dev/vite-task#888 · opened on Oct 25, 2026

• Cache replay restores outputs with their archived modification times, so mtime-based tools skip changed files

  voidzero-dev/vite-task#881 · opened on Oct 24, 2026