Tracking issue: NPM compatible version ranges

[mbrubeck]

• Implement comparison rules for pre-release tags #53 - Implement comparison rules for pre-release tags
• Allow whitespace-delimited comparator sets #55 - Allow whitespace-delimited comparator sets
• Implement hyphen ranges #56 - Implement hyphen ranges
• Support the || operator in version ranges #57 - Support the || operator in version ranges

[hone]

@isaacs Is ~= a valid semver operator? I noticed it works on https://semver.npmjs.com. I can't tell the difference between it and ~. For context, we're looking to replace a piece of functionality on Heroku with a Rust binary that does semver version resolution for node and yarn versions. In the wild we're seeing ~=14.4. /cc @danielleadams

[isaacs]

@hone So it is!

> semver.validRange('~=1.2.3')
'>=1.2.3 <1.3.0-0'

Kinda weird, imo.

[hone]

Thanks! So they are the same.

Doing a quick search, I don't see it the semver range spec changes.

[dtolnay]

As of 1.0.0, this is no longer in scope for this crate, as described by https://github.com/dtolnay/semver/tree/1.0.0-rc.1#scope-of-this-crate. A separate https://crates.io/crates/node-semver crate may or may not happen depending on who is interested in maintaining it.