feat(core): transition daemon from queue to transaction based messaging #28983
+522
−352
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
The daemon uses a serial queue to communicate with individual Nx processes. This can slow things down if things inside of a
promise.all
or similar method call the daemon multiple times, as all calls must wait for the prior call to finish before starting.Expected Behavior
The daemon utilizes a transaction based message system, such that it can respond to a message which arrived later if its able to complete quicker
Related Issue(s)
Fixes #