Order builds by package

[jeremy-giles]

Hello, I am looking for a way to first run the build of the modules of packages/*, then of features/* and finally of apps/*.
Why? because as it stands the modules of features/* use Freezed entities contained in packages/*.

name: my_app
packages:
  - packages/*
  - features/*
  - apps/*

command:
  bootstrap:
    usePubspecOverrides: true

scripts:
  pubget:
    exec: flutter clean && flutter pub get && dart pub get

  pubupgrade:
    exec: flutter pub upgrade

  build:
    run: |
      melos run build:packages && \ 
      melos run build:features && \ 
      melos run build:apps
    description: Build all packages, features and apps in this order to prevent freezed build.
    select-package:
      depends-on: build_runner

  build:packages:
    run: cd packages && dart run build_runner build --delete-conflicting-outputs
    description: Launch a fresh Build runner for packages.

  build:features:
    run: cd features && dart run build_runner build --delete-conflicting-outputs
    description: Launch a fresh Build runner for features.

  build:apps:
    run: cd apps && dart run build_runner build --delete-conflicting-outputs
    description: Launch a fresh Build runner for apps.

melos run build:packages
  └> cd packages && dart run build_runner build --delete-conflicting-outputs
     └> RUNNING

Could not find package `build_runner` or file `build_runner`

[spydon]

I would suggest to just generate all files within packages that depend on build_runner and go through with --order-dependents, so that it does the leaf dependencies first, like this for example:

  generate: >
    melos exec -c 1 --order-dependents --fail-fast --depends-on="build_runner" -- \
      dart run build_runner build --delete-conflicting-outputs

If you're having circular dependencies that won't work though.

If you have circular dependencies I would recommend that you create three categories, and then use exec on each category in order:
https://melos.invertase.dev/configuration/overview#categories
https://melos.invertase.dev/filters#--category

Currently you are trying to run build_runner outside of a dart/flutter project, hence why it doesn't find it.

[jeremy-giles]

Update to 6.2.0, build success with --order-dependents

melos run build
  └> melos exec -c 1 --order-dependents --fail-fast --depends-on="build_runner" -- \ dart run build_runner build --delete-conflicting-outputs
       
     └> SUCCESS

[spydon]

So you get success without it building anything?
Do you have circular dependencies in your project?

[jeremy-giles]

So you get success without it building anything?
Yes, the build is done well, locally as well as on the CI (Gitlab). On the other hand, we go from 3 minutes (with the previous method) to 10 minutes with this script.

Do you have circular dependencies in your project?
No, I don't think we have a circular dependency.

[spydon]

If you don't want to build the packages sequentially (which is what slows it down) I'd suggest you do it with categories as I linked in the initial reply.

[jeremy-giles]

Hi @spydon,
Updated the discussion with the progress of our build refactoring. The latter is not yet optimized but allows us to resolve dependency issues between modules.
Splitting into packages of modules without dependencies (init) or whose dependencies are already built (apps/*)

packages:
  - packages/*
  - features/*
  - apps/*

categories:
  init:
    - packages/i18n
    - packages/shared_prefs
  packages:
    - packages/utils
    - packages/api
    - packages/database
  independentFeatures:
    - features/auth
    - features/user
    - features/location
    - features/items
  features:
    - features/user_profile
    - features/catalog
    - features/dreamteam
    - features/rooms
  apps:
    - apps/*

build:
    run: |
      melos run build:init && melos run build:packages && melos run build:independentFeatures && melos run build:features && melos run build:apps

  build:init: >
    melos exec --category="init" -c 2 --fail-fast --depends-on="build_runner" -- dart run build_runner build --delete-conflicting-outputs

  build:packages: >
    melos exec --category="packages" -c 4 --fail-fast --depends-on="build_runner" -- dart run build_runner build --delete-conflicting-outputs

  build:independentFeatures: >
    melos exec --category="independentFeatures" -c 4 --fail-fast --depends-on="build_runner" -- dart run build_runner build --delete-conflicting-outputs

  build:features: >
    melos exec --category="features" -c 1 --order-dependents --fail-fast --depends-on="build_runner" -- dart run build_runner build --delete-conflicting-outputs
  
  build:apps: >
    melos exec --category="apps" -c 2 --fail-fast --depends-on="build_runner" -- dart run build_runner build --delete-conflicting-outputs