fix(web): npm dependencies from the project graph #6843
Merged
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.
get the npm dependencies from the project graph correctly. Allow deep import from
externals
passed from settingsCurrent Behavior
The npm dependencies are read incorrectly from the project graph. Also, there is no deep analysis of
external
packages, but they are matched directly by id, but the npm dependencies have this logic.Expected Behavior
The npm dependencies should be read correctly from the project graph by the project name.
externals
from the build config should allow nested imports as well as npm packages.