Make pre-release version naming align with semver 2 about react

[eps1lon]

According to semver 2 pre-release versions are supposed to be ordered by dot-separated string ordering

These versions are not ordered. Consumers of canary or rc-* versions are not supposed to use any ranges (^, ~, > etc.).

If you want to get the latest RC, you can use npm view react@rc --json versio n

[pgsandstrom]

I dont quite understand what you mean by "these versions are not ordered". Are there instances where an older version would have a newer date string? If not, than at least our issue would be resolved by my suggestion.

I understand that it would be strange to use ranges with an rc version. I also understand that npm has tags that can be used to find canary/next/rc versions. But that is not directly related to my issue.

The basic gist is: According to semver precedence of pre-releases must be determined by string ordering. It would help us if React complied with semver.

[eps1lon]

Are there instances where an older version would have a newer date string?

Meaning they're not ordered in a SemVer sense. If your application works with one Canary version, there's no "later" version that has any guarantees whether it works.

The basic gist is: According to semver precedence of pre-releases must be determined by string ordering. It would help us if React complied with semver.

That is what I mean with "there's no ordering". Given two Canary versions, there's no right precedence which version should be chosen. The "rc", "canary", "experimental" etc in these version strings are only helpers to quickly identify what release you're working with.

They do not work by design like rc.0 or canary.0. If they are, we do release them as such e.g. 19.0.0-rc.0.

[dai-shi]

fwiw, 19.0.0-rc.0 is released https://www.npmjs.com/package/react/v/19.0.0-rc.0, but it can't be used with caret.

repro:

$ npm i 'react@^19.0.0-rc.0'
$ jq .dependencies.react package.json 
"^19.0.0-rc.0"
$ grep "resolved.*react" package-lock.json
      "resolved": "https://registry.npmjs.org/react/-/react-19.0.0-rc-fb9a90fa48-20240614.tgz",

[eps1lon]

Right, I remembered that wrong. It was purely for a nicer display not to allow caret ranges.