fix(core): update getLastValueFromAsyncIterableIterator to support AsyncIterables returned from executors #23229
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.
When an executor returns an
AsyncIterable
Nx fails because it cannot read the value usinggetLastValueFromAsyncIterableIterator
(which only supportsAsyncIterableIterator
. This PR updates it to support both so executors like@nx/rollup:rollup
will work.Current Behavior
Running Nx command fails if executor returns
AsyncIterable
e.g. by callingcreateAsyncIterable
.Expected Behavior
Nx command succeeds when executor returns
AsyncIterable
.Related Issue(s)
Fixes #23028