Incorrect semver release for beta channel causes beta9 to be latest

> npm view react-select versions
[ '0.0.1',
  '0.0.2',
  …
  '0.9.1',
  '1.0.0-beta1',
  '1.0.0-beta10',
  '1.0.0-beta11',
  '1.0.0-beta12',
  '1.0.0-beta13',
  '1.0.0-beta2',
  '1.0.0-beta3',
  '1.0.0-beta4',
  '1.0.0-beta5',
  '1.0.0-beta6',
  '1.0.0-beta7',
  '1.0.0-beta8',
  '1.0.0-beta9' ]

Because versions are sorted alphabetically and not numerically. Therefore if a dependee’s package.json uses "react-select": "^1.0.0-beta13" the ^ sees the latest point release 1.0.0-beta9 as higher then the prescribed 13.

Semver gives the guidelines that beta versions be released as e.g. 1.0.0-beta.13 etc…

https://docs.npmjs.com/misc/semver#prerelease-identifiers

[bvaughn]

Great suggestion @Enet4. Instead of 1.0.0-beta.14 (or the proposed 1.0.0-beta.14 format), the next release could be versioned as 1.0.0-rc.1. I’ll re-open. Ultimately it’s up to @JedWatson but I think this is a good direction… 😃

[Enet4]

I honestly don’t believe this should be closed, as the issue still remains. In fact, I was nearly about to make a needless duplicate.

How about publishing the next version with the pre-release identifier rc (for release candidate)? It would be lexically greater than beta and still be meaningful to humans.