Skip to content

release/index.json reliability #94

@springmeyer

Description

@springmeyer

Yesterday https://iojs.org/download/release/index.json reported "modules":"44" for the v2.0.0 release which looks correct per https://github.com/iojs/io.js/blob/v2.0.0/src/node_version.h#L48.

But today the same endpoint reports 42. Any idea what changed? (I don't see any changes to https://github.com/iojs/build/commits/master/tools/dist/dist-indexer/ in the last day)

[
{"version":"v2.0.0","date":"2015-05-04","files":["linux-armv6l","linux-armv7l","linux-x64","linux-x86","osx-x64-pkg","osx-x64-tar","src","win-x64-exe","win-x64-msi","win-x86-exe","win-x86-msi"],"npm":"2.9.0","v8":"4.2.77.18","uv":"1.4.2","zlib":"1.2.8","openssl":"1.0.2a","modules":"42"},
....
]

I'm asking because for node-pre-gyp I need to get this number right. I can start parsing the node_versions.h header for all formal releases if release/index.js is not intended to be stable. But I'd sure love it to be stable. Let me know if there is something I can help with.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions