turbo watch wrong hash

[vekexasia]

Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

turborepo/examples/with-rollup

What package manager are you using / does the bug impact?

pnpm

What operating system are you using?

Linux

Which canary version will you have in your reproduction?

2.1.1

Describe the Bug

i tried the with-rollup example as it aligns with my use case.

steps:

• npx turbo build
• edit packages/ui/.eslintrc.cjs add a new line and save
• npx turbo build

this gives FULL TURBO ->>> Ok

now:

• npx turbo watch build
• make same edit

this gives a cache miss with a different hash and rebuilds

notes: if from here you npx turbo build again. the hash is the same as in the first steps

Expected Behavior

cache hits like in turbo build

To Reproduce

• clone turborepo
• cd examples/with-rollup
• pnpm i

Additional context

No response

[chris-olszewski]

turbo watch does make use of the cache to prevent any partial artifacts from being stored in the cache. I see this isn't documented anywhere so I'll quick add it.

[vekexasia]

What is the proper way to have a watch rebuild + subdeps?

[chris-olszewski]

I don't believe I understand your question. Could you elaborate a bit?

[vekexasia]

I would like something like watch that honors the inputs of the task so that it triggers only when something matching the inputs changes.

[MarkParnwell]

I believe I am having the same issue of turbo watch not respecting task inputs.

Given a turbo.json like below

{
  "$schema": "https://turbo.build/schema.json",
  "tasks": {
    "build": {
      "dependsOn": ["^build"],
      "inputs": ["$TURBO_DEFAULT$", "src/**/*.ts", "!src/**/*.spec.ts"],
      "outputs": ["dist/**"]
    }
  }
}

When I run turbo run build, change a test file and run turbo run build again, I get

 Tasks:    3 successful, 3 total
Cached:    3 cached, 3 total
  Time:    90ms >>> FULL TURBO

However, when I run turbo watch build and change a test file, the build task is re-executed each time.