add NODE_MODULE_VERSION column to the releases table

[max-mapper]

why this is valuable: https://gist.github.com/maxogden/e81e0f1d222106146828

what it looks like:

[Fishrock123]

@maxogden Correct me if I'm wrong, but isn't this better covered by https://nodejs.org/dist/index.json?

[Fishrock123]

Perhaps we should link to that json on this page?

[max-mapper]

@Fishrock123 the data you linked is that data that is used to render the table, so it's the same thing

[rvagg]

@maxogden see also nodejs/build#151 which is related to your gist

[rvagg]

lgtm, I quite like the idea of this number becoming part of user-base consciousness as it's pretty important

[fhemberger]

Can someone please add a little note on the table, what "NODE_MODULE_VERSION" is supposed to mean? Have you checked the table layout on small screens as well?

[rvagg]

we could just call it "modules version", that'd be consistent enough:

$ node -p process.versions
{ http_parser: '2.5.0',
  node: '4.1.0',
  v8: '4.5.103.33',
  uv: '1.7.4',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  modules: '46',                         <————
  openssl: '1.0.2d' }

[rvagg]

Or just "Modules", it seems confusing but with a footnote it might make sense:

‡ "Modules" refers to the ABI (application binary interface) version number of Node.js, used to determine which versions of Node.js compiled C++ add-on binaries can be loaded in to without needing to be re-compiled.

[fhemberger]

@rvagg 👍

[Fishrock123]

Rod's comment seems good.

[max-mapper]

Updated:

[Fishrock123]

NODE_MODULE_VERSION.

Might render better. (Also: period.) :)

[max-mapper]

@Fishrock123 the period is in the diff, not in the screenshot sorry. Heres what it looks like wrapped with a <code>:

And without (the current version in the branch now):

[fhemberger]

Looks better with <code> IMHO. Let's get this merged. ;)

[max-mapper]

alright, updated. should be good to go

[fhemberger]

Yaaay! Thank you! ^____^

[rvagg]

great work! I love that this is first-class, thanks @maxogden