fix(node): add workaround for handling sub processes in node:node exe… #10292
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.
…cutor
In Nx 15, we plan to clean up runExecutor and implement proper process handling in runExecutor
upstream. This is a workaround that fix some racing-condition in node:node exexecutor downstream
ISSUES CLOSED: #9305
Current Behavior
runExecutor
does not spawn a process of its own which leads to thesubProcess
variable innrwl/node:node
executor a global variable shared by concurrentrunExecutor
calls. Logic tokillCurrentProcess()
innrwl/node:node
prevents it to be ran concurrently.Expected Behavior
nrwl/node:node
should be able to run concurrently.Related Issue(s)
Fixes #9305