v0.11.12 missing from 'npm-versions.txt'

[springmeyer]

It appears that v0.11.12 is missing from http://nodejs.org/dist/npm-versions.txt even though it has been released: http://nodejs.org/dist/v0.11.12/. I noticed this when running https://github.com/mapbox/node-pre-gyp/blob/master/scripts/abi_crosswalk.js.

[springmeyer]

0.10.27 and 0.10.28 are now also released and missing from http://nodejs.org/dist/npm-versions.txt.

[davidebbo]

Indeed!

Would be great to get this file updated as we rely on it to find matching npm versions. Is the updated supposed to be automated or manual?

[trevnorris]

/cc @tjfontaine

[davidebbo]

Anyone knows where this file comes from? Is it hand built and committed in some repo (if so where?), or somehow generated from some build process?

It's a very valuable resource, and it would be nice to revive it :)

[springmeyer]

bump - @tjfontaine - able to share your plan?

[springmeyer]

with node v0.8.27 coming out and #7805 getting fixed, would love to know if its feasible for this file to also get updated? Or are their plans to remove it/not support?

[tjfontaine]

To be frank I'm not sure where npm-versions.txt was even being generated from I guess maybe @isaacs was doing it when he was updating npm?

Wouldn't it be easier for your tool to use a bit more of an authoritative source to make these decisions? I'm not particularly a fan of having to maintain such a file on the website as clearly it's easy for it to fall out of sync.

Might I suggest something like: https://raw.githubusercontent.com/joyent/node/v0.8.27-release/deps/npm/package.json

This has the added benefit that your tool could grow support to be able to be pointed to a git checkout and not need the internet at all to solve this problem.

In fact I notice that you're already doing something similar for node itself.

Is the package solving the right thing? Even though you might be targeting a specific version of node and making assumptions based on that, couldn't the target system have a different npm version installed or on the path anyway?

[davidebbo]

@tjfontaine well, it was convenient when it was being updated, which it was very consistently for quite a while (but it seems no one knows how 😄).

That being said, the alternative approach you suggest looks fine to me. We'll just need to update our scripts to go after that. Thanks!

[springmeyer]

On my end I should clarify that I am not using http://nodejs.org/dist/npm-versions.txt out of an interest in npm versions but rather as a fast way to get an official list of released node versions. I wanted to avoid the seeming complexity in the approach nvm took to search through the html response from http://nodejs.org/dist/. If npm-versions.txt is not going to be maintained then I recommend removing it and closing this ticket. But I'd love to see a simple and easy to parse node-versions.txt available.

[davidebbo]

Unfortunately, the using https://raw.githubusercontent.com/joyent/node/v0.8.27-release/deps/npm/package.json for the mapping no longer works for Node 4.0. i.e. https://raw.githubusercontent.com/joyent/node/v4.0.0-release/deps/npm/package.json doesn't exist.

Does anyone know of an alternate way to get the mapping? I know the matching npm is 2.14.2, but we need a way to automate that going forward.

[ChALkeR]

@davidebbo https://raw.githubusercontent.com/nodejs/node/v4.0.0/deps/npm/package.json works for versions v1.0.0 to v4.0.0.

[davidebbo]

@ChALkeR awesome, thanks much!

[rvagg]

https://nodejs.org/download/release/index.json might be what you're after, there's also a .tab version of this and I'm going to add more historical versions to this shortly. Generated with https://github.com/nodejs/build/tree/master/setup/www/tools/dist-indexer

[davidebbo]

@rvagg Nice! Did that always exist, or is it new? Looks like a better version of the defunct http://nodejs.org/dist/npm-versions.txt.

[rvagg]

@davidebbo new, we've been doing it with iojs.org and have only been doing it with nodejs.org for the past 2 weeks

[davidebbo]

@rvagg Thanks, it's a great resource to have for easily looking up what maps to what.