You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 32f7756
Browse filesBrowse the repository at this point in the historyBrowse files
Fix exact name treated as ambiguous in Target::ambiguity
When a bare package name like 'lodash' matched both an exact full name
(pkg:npm/lodash) and a last-segment hit (pkg:npm/@types/lodash), the
ambiguity check incorrectly flagged it as ambiguous and refused to act.
The fix checks if exactly one package has a full name that exactly
matches the typed name (case-insensitive, with PyPI canonicalization).
When such a unique exact match exists, the name is not ambiguous and
the exact match is preferred over any last-segment hits.
This preserves the existing behavior for truly ambiguous cases:
- 'core' matching both @angular/core and @babel/core (0 exact matches)
- 'six' matching both pkg:pypi/six and pkg:npm/six (2 exact matches)
While fixing the regression for common TypeScript scenarios:
- 'lodash' now correctly selects pkg:npm/lodash, not ambiguous with
@types/lodash
- 'react' now correctly selects pkg:npm/react, not ambiguous with
@types/react
0 commit comments