I'm stumped. Turbo seems to be ignoring dependency order, and I'm not using --parallel. Sometimes it builds in a workable order, sometimes it doesn't. I'm new to turborepo, attempting to port from an Nx monorepo.

{
  "$schema": "https://turbo.build/schema.json",
  "globalDependencies": ["**/.env.*local"],
  "pipeline": {
    "build": {
      "dependsOn": ["^build"],
      "outputs": ["dist/**", ".next/**"]
    },
    "test": {
      "outputs": ["coverage/**"],
      "dependsOn": []
    },
    "lint": {
      "outputs": []
    },
    "dev": {
      "cache": false
    },
    "clean": {
      "cache": false
    }
  }
}

Relevant portion of the dependency graph:

When I run turbo clean build:

database/package.json:

  "dependencies": {
    "@fieldzoo/config": "*",
    "@fieldzoo/utilities": "*"
  },

config/package.json:

  "dependencies": {
    "@fieldzoo/utilities": "*",
    "@fieldzoo/validation": "*",
    "@fieldzoo/validators": "*"
  },

validation/package.json:

  "dependencies": {
    "@fieldzoo/utilities": "*"
  },

When it gets the build order right, everything compiles just fine. I can also manually compile them in the proper order without problem.