Node.js stable now it's v0.12.0, but it's shown as unstable while at the same time the stable one is set to v0.10.35. I think stable should point to 0.12.0and unstable to 0.11.16 or at least to 0.12.0, too.

Many people & projects (like Angular) are now using yarn instead of npm so it'd be cool if semver.io supported it.

Node.js follows semver; versions below 1.0.0 technically don't have to abide to anything and the first Node with version >=1.0.0, i.e. 4.0.0 will not have pre-releases marked by minor numbers.

This check should be corrected.

/cc @zeke :)

New version of node released with critical security update ~18h ago:-
https://twitter.com/nodejs/status/617163261901844480

But not yet appearing on semver.io:-
https://semver.io/node/resolve?range=undefined
(returns v0.12.5)

It looks like the URL used for updates has the version on it:-

http://nodejs.org/dist/

Maybe the dyno just needs restarting?

https://semver.io/node/resolve/5.10.x returns the incorrect result, returning 5.10.0. The latest released version matching this range is 5.10.1 so I presume the result should either be

5.10.0
5.10.1

if it is meant to show all matches, or

5.10.1

if it is meant to return the latest version. The node-semver command line behaves as expected

[emkman@Ethans-MacBook-Pro  ~]$ semver 5.10.0 5.10.1 -r 5.10.x
5.10.0
5.10.1

It seems like the Node stable and unstable have been mixed up.

https://semver.io/node/stable => 5.11.1
https://semver.io/node/unstable => 6.2.1

I would expect the LTS version (6.2.1) to be the stable version. Is this the expected behaviour? I don't mind giving the code a jab to fix things up, I just wanted a heads-up before I do so.

@hunterloftis

I assume it doesn't show up under https://semver.io/node.json as stable as you accept each release manually? Otherwise 4.0.0 should be recognized as stable.

it seems to be resolving to 0.10.21 at the moment

If I put in a pull to add from this dist site, would that be something you all would consider adding to the project?

The semver.io app currently downloads the latest info from nodejs.org at startup. In order to keep the node version information more fresh, I want to restart every fifteen minutes or so, instead of once a day when the dynos roll.

@jclem @ddollar, how would you go about this? Heroku Scheduler + an npm task? Modify the app to make it re-initialize itself?

Sometimes this route will load the data I expect, but sometimes it will not. Refreshing the browser seems to randomly provide valid or invalid responses. This happens for Yarn and NPM, but not the others, as far as I can tell.

https://semver.io/yarn.json

https://semver.io/npm.json

{"all":[],"stableVersions":[]}

{"stable":"1.16.0","unstable":"1.16.0","all":["0.1.0","0.1.1","0.1.2","0.1.3","0.15.1","0.16.0","0.16.1","0.17.0","0.17.2","0.17.3","0.17.4","0.17.5","0.17.6","0.17.7","0.17.8","0.17.9","0.17.10","0.18.0","0.18.1","0.18.2","0.19.0","0.19.1","0.20.0","0.20.3","0.20.4","0.21.0","0.21.1","0.21.2","0.21.3","0.22.0","0.23.0","0.23.1","0.23.2","0.23.3","0.23.4","0.24.0","0.24.1","0.24.2","0.24.3","0.24.4","0.24.5","0.24.6","0.25.1","0.25.2","0.25.3","0.25.4","0.26.0","0.26.1","0.27.0","0.27.1","0.27.2","0.27.3","0.27.4","0.27.5","0.28.1","0.28.4","1.0.0","1.0.1","1.0.2","1.1.0","1.2.0","1.2.1","1.3.1","1.3.2","1.4.0","1.5.0","1.5.1","1.6.0","1.7.0","1.8.0","1.9.1","1.9.2","1.9.4","1.10.0","1.10.1","1.11.0","1.11.1","1.12.0","1.12.1","1.12.3","1.13.0","1.14.0","1.15.0","1.15.1","1.15.2","1.16.0"],"stableVersions":["0.1.0","0.1.1","0.1.2","0.1.3","0.15.1","0.16.0","0.16.1","0.17.0","0.17.2","0.17.3","0.17.4","0.17.5","0.17.6","0.17.7","0.17.8","0.17.9","0.17.10","0.18.0","0.18.1","0.18.2","0.19.0","0.19.1","0.20.0","0.20.3","0.20.4","0.21.0","0.21.1","0.21.2","0.21.3","0.22.0","0.23.0","0.23.1","0.23.2","0.23.3","0.23.4","0.24.0","0.24.1","0.24.2","0.24.3","0.24.4","0.24.5","0.24.6","0.25.1","0.25.2","0.25.3","0.25.4","0.26.0","0.26.1","0.27.0","0.27.1","0.27.2","0.27.3","0.27.4","0.27.5","0.28.1","0.28.4","1.0.0","1.0.1","1.0.2","1.1.0","1.2.0","1.2.1","1.3.1","1.3.2","1.4.0","1.5.0","1.5.1","1.6.0","1.7.0","1.8.0","1.9.1","1.9.2","1.9.4","1.10.0","1.10.1","1.11.0","1.11.1","1.12.0","1.12.1","1.12.3","1.13.0","1.14.0","1.15.0","1.15.1","1.15.2","1.16.0"],"updated":"2019-06-06T16:07:40.066Z"}

This was causing our CI builds to fail.

Should currently be 7.4.0. ^6.0.0 is also returning 6.9.1 but it should be 6.9.3.

Similar to #57 but that's apparently fixed.

curl https://semver.io/yarn/stable 1

Returns 1.5.0 which is a pre-release. Its also not available for download yet. This is breaking build and deploy scripts.

The latest release is 5.3.0, semver.io reports 5.1.1.

FWIW, processing https://nodejs.org/dist/index.json might be easier and more robust than scraping https://nodejs.org/dist/

This is a great tool and is quite helpful for the nodenv ecosystem. @hurrymaplelad built a plugin for nodenv that lets nodenv pull its version from package.json engines instead of .node-version. It is using this service to determine the best node version that satisfies the version spec from engines. However, that's only half the puzzle for nodenv. In addition to simply finding the maximum version match for a given semver range, we would like to take into account versions that are installed.

I would love to see the ability to pass a semver range and also a list of versions, and have semver.io select the best option available from the provided list (defaulting to current behavior if none match).

Since this would be an optional extra parameter (array), then omitting it does not alter current behavior.

Example:

https://semver.io/node/resolve?range=>%3D4.0.0
5.0.0

https://semver.io/node/resolve?range=>%3D4.0.0&v=4.2.1
4.2.1

https://semver.io/node/resolve?range=>%3D4.0.0&v=4.0.0&v=4.1.0&v=4.2.1
4.2.1

https://semver.io/node/resolve?range=>%3D4.0.0&v=0.10.0&v=0.12.0
5.0.0

Thoughts?

Node.js >=4 pre-releases are kept in different directories than the release ones. For example Node.js 4.0.0-rc.1 is kept under https://nodejs.org/download/rc/. This makes http://semver.io/node.json not detect it and still claim 0.12.7 is the latest version, including unstable ones.

In the old days (2013), it was fine to just roll with the version of npm that came bundled with node, but nowadays npm is released on a faster cycle than node. As such, it would be nice to have a webservice for querying available npm versions. Hey that's what semver.io is for!

@othiym23, @bcoe, @ceejbot could we use the GitHub releases API to fetch all the versions?

❯ curl --get --data-urlencode "range=2.5.x" https://semver.herokuapp.com/iojs/resolve
4.0.0

This is causing Heroku deploys to fail for iojs:

remote: -----> Installing binaries
remote:        engines.iojs (package.json):  2.5.x (iojs)
remote:        engines.npm (package.json):   unspecified (use default)
remote:
remote:        Resolving iojs version 2.5.x via semver.io...
remote:        Downloading and installing iojs 4.0.0...
remote:        Unable to download iojs 4.0.0; does it exist?
remote:
remote: -----> Build failed
remote:
remote:        We're sorry this build is failing! You can troubleshoot common issues here:
remote:        https://devcenter.heroku.com/articles/troubleshooting-node-deploys
remote:
remote:        If you're stuck, please submit a ticket so we can help:
remote:        https://help.heroku.com/
remote:
remote:        Love,
remote:        Heroku
remote:
remote:
remote:  !     Push rejected, failed to compile Node.js app

https://semver.io/node/resolve/%3E=4

engines.node of >= 4 should resolve to the latest version of node, which is 6.5.0, not 5.11. yes? I think 5.x series is nearly EOL already.

If I am wrong, then I'd appreciate any insight on how to write "the largest version number and also greater than 4.0". thanks

Requests to https://semver.io/node/versions and other end points are yielding different results when manually refreshing in the browser.

The Node.js and io.js projects have merged and had their first unified release: Node 4.0.0

In October 2015 the Node Foundation will take a snapshot of the then stable version of v4 (eg. 4.1.7) which will become the first LTS (Long Term Support) version of Node with support until April 2017. At the same time a pre-release version Node 5.0.0 will be made available.

This issue is here to track suggestion for how semver.io will handle pre-release and LTS versions of Node post v4.0.0 now that Node has moved away from it's linux style odd:unstable::even:stable versioning system and is now SemVer compliant.

Hi @jmorrell !!!

I want to open a PR documenting support for the range query param:

$ curl "https://semver.io/node/resolve/?range=^8.3.0"
8.11.1

Before I do so, just want to make sure it's wanted, and that it has a chance of being merged :)

Are these updated manually now? If so, I can submit a PR with latest results.

curl https://semver.io/node/stable
0.10.33

curl https://semver.io/node/unstable
0.11.14

curl https://semver.io/node/resolve/0.8.x
0.8.28

curl https://semver.io/nginx/stable
1.6.2

This project has been deprecated since 2019 (#69), and the Heroku instance of the project is due to be switched off shortly.

As such, any consumers of https://semver.io, https://www.semver.io or https://semver.herokuapp.com should migrate to another solution, or host their own version of the site using the source here.

Alternatively, if all you need is a list of Node.js versions or to find out which is the latest (rather than semver range expression parsing etc), you could use one of these newer options directly:
https://nodejs.org/dist/index.json
https://raw.githubusercontent.com/nodejs/Release/main/schedule.json
https://www.npmjs.com/package/node-release-lines

If you are using a buildpack and are getting semver.io related errors - you are likely pinned to an outdated version tag of a buildpack, or using an unmaintained fork. Switch to an official/maintained buildpack instead:
https://devcenter.heroku.com/articles/buildpacks#officially-supported-buildpacks

Node.js 0.12.4 is the latest patch release for Node.js 0.12, it's not unstable and yet http://semver.io/node.json shows it as such, claiming latest stable version is 0.12.3.

Why is that?

The IoJsSource.prototype._parse function incorrectly assumes that a non-even minor means the version is unstable. This was only a valid convention for Node.js, it was never valid for io.js. All io.js versions are considered final & stable. io.js follows semver.

In particular, this incorrectly marks io.js 2.1.0 as unstable.

The logic should be removed in the io.js case.

Hey @danieltdt, check out https://semver.io/nginx.json

The recent versions are repeating.

The latest version of NodeJS is 5.1.0 but https://semver.io/node/stable says 5.0.0

I don't find a license file or anything mentioned in README. zeke, could you please add one?