run-many order

[j]

Description

I'd like the ability to run a specific target match last.

Motivation

I have an API gateway that needs to run after all other services are running. Right now nx chooses the gateway first and it fails to launch due to how Apollo Federation works.

[FrozenPandaz]

The order of run-many is based on the dependencies between projects. If you need a project which needs to wait for all other projects, you can specify that the project implicitly depends on other projects using Implicit Dependencies.

If you want to start up the API Gateway and knowing it depends on starting its dependencies:
Having configured it with the above, you can set a Target Dependency that tells the API Gateway to also need the serve of its dependencies.

Alternatively, you can exclude the API Gateway from the run-many by passing --exclude api-gateway. Then, run nx serve api-gateway afterwards.

If these don't make sense, I recommend joining the Community Slack channel where someone can help you more synchronously than a Github Issue.
http://go.nrwl.io/join-slack

[j]

Yup, I did the later one you mentioned. I’ll try the other methods. I now ping the services in the gateway in development to wait until they are live.

…

On Mon, Jul 5, 2021 at 3:07 PM Jason Jean ***@***.***> wrote: Closed #6182 <#6182>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6182 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEP4YVS4JFNOTEYMY7N24DTWIUJRANCNFSM47Q6TAMQ> .

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.