How to specify which order should run the build task of package #1347

tgmarinho · 2022-06-07T20:44:03Z

tgmarinho
Jun 7, 2022

how to set up the turborepo to run the build scripts from each package.json of the packages repo in some specific order?

I have the packages: a, b, c, I wanna run the build in this order: b,c, a

I think the answer is here: https://turborepo.org/docs/core-concepts/pipelines#implicit-dependencies-and-specific-package-tasks But I couldn't figure out it yet, my suggestion, if possible, is to have some example package with this setup.

https://twitter.com/tgmarinho/status/1534272696963538946

Answered by ThibautMarechal

Jun 8, 2022

You have 2 options:

1) Make that link visible in each package dependencies

(C depends on B and A depdends on C)

{
  "name": "a",
  "dependencies": {
    "c": "*"
  },
  "scripts": {
    "build": "echo a"
  }
}

{
  "name": "b",
  "scripts": {
    "build": "echo b"
  }
}

{
  "name": "c",
  "dependencies": {
    "b": "*"
  },
  "scripts": {
    "build": "echo c"
  }
}

Then you just need to configure the pipelines with the ^ before the task's name.

{
  "$schema": "https://turborepo.org/schema.json",
  "pipeline": {
    "build": {
      "dependsOn": ["^build"]
    }
  }
}

2) Make that link visible in the `turbo.json` file

(no package depends on each others)

{
  "name": "a",
  "scripts": {
  …

View full answer

ThibautMarechal · 2022-06-08T19:00:14Z

ThibautMarechal
Jun 8, 2022

You have 2 options:

1) Make that link visible in each package dependencies

(C depends on B and A depdends on C)

{
  "name": "a",
  "dependencies": {
    "c": "*"
  },
  "scripts": {
    "build": "echo a"
  }
}

{
  "name": "b",
  "scripts": {
    "build": "echo b"
  }
}

{
  "name": "c",
  "dependencies": {
    "b": "*"
  },
  "scripts": {
    "build": "echo c"
  }
}

Then you just need to configure the pipelines with the ^ before the task's name.

{
  "$schema": "https://turborepo.org/schema.json",
  "pipeline": {
    "build": {
      "dependsOn": ["^build"]
    }
  }
}

2) Make that link visible in the `turbo.json` file

(no package depends on each others)

{
  "name": "a",
  "scripts": {
    "build": "echo a"
  }
}

{
  "name": "b",
  "scripts": {
    "build": "echo b"
  }
}

{
  "name": "c",
  "scripts": {
    "build": "echo c"
  }
}

(build of C depends on build of B and build of A depdends on build of C)

{
  "$schema": "https://turborepo.org/schema.json",
  "pipeline": {
    "a#build": {
      "dependsOn": ["c#build"]
    },
    "b#build": {},
    "c#build": {
      "dependsOn": ["b#build"]
    }
  }
}

I personally prefer the first solution, but I guess it depends on the use case 😄

1 reply

Neo-Ciber94 Jul 7, 2024

The 1st solution didn't work for me, but the second one does.

Thank!

arkmech · 2023-09-01T00:02:45Z

arkmech
Sep 1, 2023

I tried this out with dev script tsup --watch, but it stalls on the dependent package because I guess turborepo can't tell if its done. Since its in watch mode, Even though tsup build outputs: DTS ⚡️ Build success in 3039ms

4 replies

58bits Sep 15, 2023

Hi @arkmech - I'm having the same problem. Did you find a solution? I'd like the package with tsup --watch to execute first, and then watch, and then build the other packages.

arkmech Sep 15, 2023

@58bits, I ended up solving the issue with a workaround. I had the clean option in tsup config which only cleans declaration files it seems. It does take a good amount of time to build type declaration files for my other packages that depend on it. This causes all my watch builds to fail.

So I just removed the clean option and I'm all set with this issue.

58bits Sep 15, 2023

Ah I see - thanks - I'll give it a try.

anthonyshew Jul 7, 2024
Maintainer

turbo watch is unable to know when a built-in task watcher (like tsup --watch) has completed it's work. Since it's a persistent task, it has no "end" state.

Instead, you likely want to use tsup (without --watch) and make sure the task isn't marked as persistent.

tgmarinho · 2022-06-10T18:06:56Z

tgmarinho
Jun 10, 2022
Author

https://www.tgmarinho.com/posts/2022-06-09-deploy-monorepo-turborepo-heroku

0 replies

buster95 · 2025-09-06T18:14:31Z

buster95
Sep 6, 2025

In the last version of turbo repo pipeline isnt recognized so you can do this

{
    "$schema": "https://turborepo.com/schema.json",
    "ui": "tui",
    "tasks": {
        "build": {
            "outputs": [
                "dist/**"
            ]
        },
        "fronty#build": {
            "dependsOn": [
                "backy#build"
            ]
        },
        "check-types": {
            "dependsOn": [
                "^check-types"
            ]
        },
        "dev": {
            "persistent": true,
            "cache": false
        }
    }
}

0 replies

How to specify which order should run the build task of package #1347

Uh oh!

Uh oh!

1) Make that link visible in each package dependencies

2) Make that link visible in the turbo.json file

Replies: 4 comments · 5 replies

Uh oh!

1) Make that link visible in each package dependencies

2) Make that link visible in the turbo.json file

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

anthonyshew Jul 7, 2024 Maintainer

Uh oh!

tgmarinho Jun 10, 2022 Author

Uh oh!

2) Make that link visible in the `turbo.json` file

Replies: 4 comments 5 replies

2) Make that link visible in the `turbo.json` file

anthonyshew Jul 7, 2024
Maintainer

tgmarinho
Jun 10, 2022
Author