"missing tasks" when using root task + filters

[benjick]

Verify canary release

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

Link to code that reproduces this issue

https://github.com/benjick/missing-tasks-filter-root-repro

Which canary version will you have in your reproduction?

2.3.4-canary.2

Enviroment information

turbo info
turbo 2.3.4-canary.2

CLI:
   Version: 2.3.4-canary.2
   Path to executable: /Users/max/dev/missing-tasks-filter-root-repro/node_modules/.pnpm/[email protected]/node_modules/turbo-darwin-arm64/bin/turbo
   Daemon status: Running
   Package manager: pnpm

Platform:
   Architecture: aarch64
   Operating system: macos
   WSL: false
   Available memory (MB): 14359
   Available CPU cores: 10

Environment:
   CI: None
   Terminal (TERM): xterm-256color
   Terminal program (TERM_PROGRAM): WarpTerminal
   Terminal program version (TERM_PROGRAM_VERSION): v0.2024.12.10.15.55.stable_03
   Shell (SHELL): /opt/homebrew/bin/fish
   stdin: false

Expected behavior

When running turbo run --filter=!pkg-b build root, where root is a root task ("//#root") I expected turbo to execute the task

Actual behavior

  × missing tasks in project

Error:   × could not find task `root` in project

To Reproduce

Clone https://github.com/benjick/missing-tasks-filter-root-repro
run pnpm error

Additional context

It works if I run turbo run --filter=!pkg-b build //#root

[ahsath]

I sort of have the same error.

e.g. I have 3 apps, 2 of them with

  "scripts": {
    "dev": "vite"

and one with

  "scripts": {
    "dev": "npm run server:dev",
    "server:dev": "npm run server",

if I understand when defining root tasks, e.g. dev turborepo will search all packages.json files for scripts that matches the name for the same task name, but for some reason I get missing scripts

My turbo.json pretty straighforward

{
  "$schema": "https://turbo.build/schema.json",
  "globalDependencies": ["**/.env.*local"],
  "tasks": {
    "build": {
      "dependsOn": ["^build"],
      "outputs": ["dist/**"]
    },
    "lint": {
      "dependsOn": ["^lint"]
    },
    "dev": {
      "cache": false,
      "persistent": true
    }
  }
}

Only one script successfully runs (see image attachment), I am not quite sure if it is a Vite issue regarding ports (race condition), tried changing the port on each project (didn't work), although this missing scripts does not always occurs, I think it has to do with the ports these apps are running because if I restart my computer it runs fine for a couple of times but if I exit turbo and run it again, it errors out with missing scripts. It is like turborepo is trying to execute scripts from one project into another if all registered scripts do not match the same CLI tool you use, in my case is Vite.

[benjick]

What error do you get?

[ahsath]

reinstalled everything, updated dependencies and I no longer get this missing scripts errors

[ethanresnick]

I'm having a similar error, but when using --affected (which I assume is desugaring to/leveraging the same --filter machinery). I.e., if I run

turbo run x --affected

Where x is only defined as a root task, and --affected filters out the root project, I get a missing task error

[ej-shafran]

@ethanresnick running into the same problem...

I'm wondering - has anyone figured out a solution for this? Right now if I want to use --affected I have to move all my root package scripts into the packages themselves, or else they won't be run for every pull request... Some of my scripts can't be run that way (https://knip.dev) so I would love for something like --affected-plus-root to be available...

[benjick]

@ej-shafran I run knip inside the packages, works great

[ej-shafran]

I run knip inside the packages, works great

So just without using the workspaces feature that's built into it...?

[benjick]

@ej-shafran exactly, then each package#knip is cached