fix(nm): Disallow overwriting workspace dependencies with portal dependencies #3590
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.
What's the problem this PR addresses?
This is a follow-up PR to #3438. There might be a problem when both workspace and portal are pointing to the same location. In this case, the ambiguity for the nm linker occurs, which one to use. It should give priority to a workspace because
devDependencies
will not be installed forportal:
How did you fix it?
When two locators point to the same soft location, I give priority to the workspace locator.
The problem was discovered by: @missing1984
Checklist