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
BREAKING CHANGE: `x` and `x@` now return the same spec as `x@*`
From #45:
Right now, `name@` and `name` are parsed with
`{type:'tag', fetchSpec: 'latest'}`, but `name@*` is parsed as
`{type: 'range'}`.
But since `''` is a valid semver range, it should be parsed the same as
`*`.
This also saves npm-package-arg from guessing the default tag, which
currently poses some semantic hazards. npm (via npm-pick-manifest) will
prefer its default tag if given a range that includes it. But
`name@latest` should always and only resolve to that specific version in
the dist-tags. So npm-pick-manifest and pacote have to detect this and
do some extra work to figure out if `latest` was actually specified or
just guessed as a default.
Closesnpm/statusboard#460
0 commit comments