You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nx pipeline correctly waits for the "Starting Offline SQS" string to appear, but then it seemingly just kills both the SQS and API when the serve task begins.
Expected Behavior
When I run the needed tasks in a single command like so:
Then it works fine and I can continue to run tests. Am I missing something obvious here? Is readyWhen designed to end a child process when it matches on the string? If so that is a bit unexpected (still learning the NX way of things, apologies if I'm out of step here).
The behaviour I'm looking for is to always run the 1st task (local which serves the backend and API) and then execute the 2nd configurable task (serve:sales or serve:holiday-letting).
Bonus Qs:
is it possible to get NX to run the commands in parallel but still output to different shells i.e. I see 4 terminals from within the VS Code terminal tab?
is it possible to get NX to share the depended upon task? What I mean is, if run serve:holiday-letting from the NX console and also run serve:sales in another terminal, will the 2nd task see that there is already a running backend and API and know not to spin up an extra one?
Thanks for your time and patience in this matter peeps, so far love the work 🚀
GitHub Repo
No response
Steps to Reproduce
Provided config demonstrates how to reproduce issue.
Current Behavior
I have some core tasks that need to be run before running specs. I am using the
dependsOn
andreadyWhen
options with the aim of:Here's the config:
The nx pipeline correctly waits for the "Starting Offline SQS" string to appear, but then it seemingly just kills both the SQS and API when the
serve
task begins.Expected Behavior
When I run the needed tasks in a single command like so:
Then it works fine and I can continue to run tests. Am I missing something obvious here? Is
readyWhen
designed to end a child process when it matches on the string? If so that is a bit unexpected (still learning the NX way of things, apologies if I'm out of step here).The behaviour I'm looking for is to always run the 1st task (
local
which serves the backend and API) and then execute the 2nd configurable task (serve:sales
orserve:holiday-letting
).Bonus Qs:
serve:holiday-letting
from the NX console and also runserve:sales
in another terminal, will the 2nd task see that there is already a running backend and API and know not to spin up an extra one?Thanks for your time and patience in this matter peeps, so far love the work 🚀
GitHub Repo
No response
Steps to Reproduce
Provided config demonstrates how to reproduce issue.
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: