BREAKING CHANGE(spec): Normalize x, x@ & x@*
#460
Comments
darcyclarke
changed the title
x, x@ & x@*x, x@ & x@*
wraithgar
added a commit
to npm/npm-package-arg
that referenced
this issue
Sep 1, 2022
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. Closes npm/statusboard#460
wraithgar
added a commit
to npm/npm-package-arg
that referenced
this issue
Sep 29, 2022
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. Closes npm/statusboard#460
wraithgar
added a commit
to npm/npm-package-arg
that referenced
this issue
Oct 12, 2022
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. Closes npm/statusboard#460
ghiscoding
added a commit
to lerna-lite/lerna-lite
that referenced
this issue
Oct 21, 2022
- npa will no longer return "latest" when passing `*` but instead it will return empty string "" as per their new v10 PR: npm/statusboard#460
ghiscoding
added a commit
to lerna-lite/lerna-lite
that referenced
this issue
Oct 21, 2022
* fix(deps): npm-package-arg now normalize x, x@, x@* - npa will no longer return "latest" when passing `*` but instead it will return empty string "" as per their new v10 PR: npm/statusboard#460
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original issue: npm/npm-package-arg#45
The text was updated successfully, but these errors were encountered: