Hi Murderlon,

This is a common challenge with Turbo when you have a peer dependency that many packages rely on, like @uppy/core. Turbo automatically orders builds based on dependencies in package.json, but peerDependencies aren’t considered by default in the task graph.

Why your current approach causes issues
When you add "dependsOn": ["@uppy/core#build"] in your package-specific turbo.json, Turbo treats that as the only dependency for the task, ignoring the implicit ones from package.json.

This can break ordering and cause race conditions because other dependencies might not be built before the package.

Recommended approaches
Centralize dependency info in root turbo.json
Instead of adding dependsOn in every package, define it in the root turbo.json under "pipeline" or "tasks" for build with a global override that includes @uppy/core#build. This way, Turbo merges implicit dependencies from package.json and your manual override.

Convert peerDependencies to explicit dependencies during build
If feasible, convert peer dependencies you want built first into dev or regular dependencies temporarily, so Turbo sees them naturally.

Explicitly list all dependencies in turbo.json
If you want full control, you can manually specify all dependencies in the root turbo.json for each package’s build task, but this is error-prone and hard to maintain.

Use the dependsOn array carefully
If you do override dependsOn, make sure to include both the ^build (to depend on all dependencies) and @uppy/core#build explicitly:

{
  "tasks": {
    "build": {
      "dependsOn": ["^build", "@uppy/core#build"]
    }
  }
}

This tells Turbo to build dependencies as usual (^build) plus @uppy/core first.

Summary

• Prefer handling this globally at the root level.
• Combine implicit dependencies (^build) with explicit ones.
• Avoid redundant per-package turbo.json if possible.