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 }}
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.
If the user provides an install range, and savePrefix + resolvedVersion is not a subset of that supplied version range, then we should save the supplied version range rather than using the savePrefix.
For example:
npm i foo@'1.x <1.2'
# resolves to foo@1.1.2, should save as '1.x <1.2' rather than '^1.1.2', because not a subset
npm i foo@'>1.0.0'
# resolves to foo@1.1.2, should save as '^1.1.2', because that's a subset of supplied range
The text was updated successfully, but these errors were encountered:
If a user installs `foo@1.x <1.2.3`, and we resolve to `1.2.2`, then we
should not save it as `^1.2.2`, since that would allow versions outside
of the requested range.
Explicit versions and tags are still saved using the savePrefix, since
those are not ranges, and users can set `--save-exact` if they wish it
to be saved exactly.
Fix: #127Fix: npm/cli#193
Fix: https://npm.community/t/7005
If a user installs `foo@1.x <1.2.3`, and we resolve to `1.2.2`, then we
should not save it as `^1.2.2`, since that would allow versions outside
of the requested range.
Explicit versions and tags are still saved using the savePrefix, since
those are not ranges, and users can set `--save-exact` if they wish it
to be saved exactly.
Fix: #127Fix: npm/cli#193
Fix: https://npm.community/t/7005
re: npm/cli#193
If the user provides an install range, and
savePrefix + resolvedVersion
is not a subset of that supplied version range, then we should save the supplied version range rather than using thesavePrefix
.For example:
The text was updated successfully, but these errors were encountered: