(🐞) Semver calculator acts differently to npm in regards to pre releases

[KotlinIsland]

• See [BUG] pre-release versions not matched when using || npm/node-semver#605

"typescript": "^5 || ^5.3.0-0"

This value will match all stable versions of 5, and all pre-releases of 5.3.0.

Proof

{
  "name": "test-npm",
  "version": "1.0.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "test-npm",
      "version": "1.0.0",
      "dependencies": {
        "typescript": "^5 || ^5.3.0-0"
      }
    },
    "node_modules/typescript": {
      "version": "5.3.0-dev.20230913",
      "resolved": "https://registry.npmjs.org/typescript/-/typescript-5.3.0-dev.20230913.tgz",
      "integrity": "sha512-+1lrLCj/NdyBbWXK3ifRSzmg0pSg2WLDmzeXf1/vTOb84eV/TCJ1i9eOS4c40T3tzDSAOjP39x9/+unUakbuKA==",
      "bin": {
        "tsc": "bin/tsc",
        "tsserver": "bin/tsserver"
      },
      "engines": {
        "node": ">=14.17"
      }
    }
  }
}

But when we look on the website, it says that it won't match the pre-releases:

According to a comment by @mbtools, this is intentional, but to me seems like it will only ever cause confusion.

[IanVS]

I think that might be because the website does not show pre-releases at all, ever, now (https://github.com/npm/feedback/discussions/995).

[mbtools]

Not entirely true. It includes pre-releases, if a condition includes pre-releases.

[IanVS]

Ah, ok.

I probably had checked a range like this (there are 5.0.0-beta.X):

Which is fine for peerDependencies, but acts differently for installing a package fresh, I guess. It feels like the calculator website should have a "peerDependencies" mode, since that's usually when things get really tricky.