fix(angular): use the browserTarget to calculate project deps for buildable libs support in the dev server #13275
+8
−3
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
webpack-dev-server
builder, when handling the incremental build scenario, is not using thebrowserTarget
name to calculate the buildable project dependencies. This causes the builder to not collect any buildable libraries and build them from the source even when thebuildLibsFromSource
option is set tofalse
.This is a regression introduced in #12924 where the following was missed https://github.com/nrwl/nx/pull/12924/files#diff-39a45d5a12bd4b48ebc0871fab97966eab51e70137d4e1d48df18ee5171b5da2L83.
Expected Behavior
The
webpack-dev-server
builder when handling the incremental build scenario, should use thebrowserTarget
name to calculate the buildable project dependencies.Related Issue(s)
Fixes #