chicoxyzzy / node-releases

Node.js releases data

Node.js releases data

All data is located in data directory.

data/processed contains envs.json with node.js releases data preprocessed to be used by Browserslist and other projects. Each version in this file contains only necessary info: version, release date, LTS flag/name, and security flag.

data/release-schedule contains release-schedule.json with node.js releases date and end of life date.

Installation

npm install node-releases

node-releases's Issues

Publish updated data containing the Node.js v16 release

It's been a few days since the Node.js v16 release, yet the updated data hasn't been published:

https://unpkg.com/node-releases/data/processed/envs.json

Error: Unexpected token

I am using Svelte with Nollup, when i'm trying to build my project with dev configuration, it throw this error (view the image to know where the error is):

ParseError: /node_modules/node-releases/data/release-schedule/release-schedule.json
SyntaxError: Unexpected token (1:7)
    {"v0.8":{"start":"2012-06-25","end":"2014-07-31"},"v0.10":{"start":"2013-03-11","end":"2016-10-31"},"v0.12":{"start":"2015-02-06","end":"2016-12-31"},"v4":{"start":"2015-09-08","lts":"2015-10-12","maintenance":"2017-04-01","end":"2018-04-30","codename":"Argon"},"v5":{"start":"2015-10-29","maintenance":"2016-04-30","end":"2016-06-30"},"v6":{"start":"2016-04-26","lts":"2016-10-18","maintenance":"2018-04-30","end":"2019-04-30","codename":"Boron"},"v7":{"start":"2016-10-25","maintenance":"2017-04-30","end":"2017-06-30"},"v8":{"start":"2017-05-30","lts":"2017-10-31","maintenance":"2019-01-01","end":"2019-12-31","codename":"Carbon"},"v9":{"start":"2017-10-01","maintenance":"2018-04-01","end":"2018-06-30"},"v10":{"start":"2018-04-24","lts":"2018-10-30","maintenance":"2020-05-19","end":"2021-04-30","codename":"Dubnium"},"v11":{"start":"2018-10-23","maintenance":"2019-04-22","end":"2019-06-01"},"v12":{"start":"2019-04-23","lts":"2019-10-21","maintenance":"2020-11-30","end":"2022-04-30","codename":"Erbium"},"v13":{"start":"2019-10-22","maintenance":"2020-04-01","end":"2020-06-01"},"v14":{"start":"2020-04-21","lts":"2020-10-27","maintenance":"2021-10-19","end":"2023-04-30","codename":"Fermium"},"v15":{"start":"2020-10-20","maintenance":"2021-04-01","end":"2021-06-01"},"v16":{"start":"2021-04-20","lts":"2021-10-26","maintenance":"2022-10-18","end":"2024-04-30","codename":"Gallium"},"v17":{"start":"2021-10-19","maintenance":"2022-04-01","end":"2022-06-01"},"v18":{"start":"2022-04-19","lts":"2022-10-25","maintenance":"2023-10-18","end":"2025-04-30","codename":""}}
           ^
    at compileModule (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:211:19)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async compileModule (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:208:13)
    at async compileModule (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:208:13)
    at async compileModule (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:208:13)
    at async compileModule (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:208:13)
    at async compileModule (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:208:13)
    at async compileModule (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:208:13)
    at async compileInputTarget (/home/risal/WebProjects/si-mantu-mantap-web/hosting/node_modules/nollup/lib/impl/NollupCompiler.js:243:5)

Please add a description of what this package does (in the README)

I have no idea what this package is for and the README did not help me to understand that.

Node 11

@chicoxyzzy Node 11 was released. We need add it to releases.

Node 13.10.1 missing from env.json

Looks like the process isn't grabbing the latest patch, and still has 13.10.0 in the env.json
Is the idea of the env.json contains just the latest patch version for each Major.Minor, or is there some other issue i'm hitting?

support for node environments

this maybe off topic, but it would be neat to have node environments supported similar to browsers, but rather for cloud environments that use different versions of node. I am not sure if this overkill or a real thing, but figured I would at least bring it up.

I am thinking places such as:

• AWS Lambda (currently v4.3.2)
• Google Cloud Functions (currently v6.9.1)
• IBM OpenWisk (currently v6.9.1)
• Azure Functions (currently v5.9.1)

Node.js 20 release

Can we release this commit? cd69bda

I need it for browserslist/browserslist#756

Add the Unnoficial Builds values

There are now a separate release chain of "unofficial builds" for some non-Tier 1 release plat forms https://github.com/nodejs/unofficial-builds.
It also has it's own index.json that can be found here https://unofficial-builds.nodejs.org/download/release/index.json

Include extra fields

Add extra info from allVersions.json file when fetching it, specifically v8 version.

Implement automatic data updates

Idea: implement bot which will create new PR for review based on information from CI daily cron job. Not sure if it's possible. We should check. Other ideas are welcome.

Add the ChakraCore releases

The are stored outside the main download directory in https://nodejs.org/download/chakracore-release/
This release-line is also halted AFAIK, but I guess it's the same case for the iojs one now too.

Automate publish of new versions

Nightly has added info for Node.js 20.3.0 two weeks ago, but latest published version in npm is of one month ago with info up to Node.js 20.2.0. I think publish of new packages should be done automatically as part of the nightly script.

Also, I think versioning of package should be the same of the highest Node.js version, or the date info was fetch (2023.6.25, for example), to make it easier to identify.

Missing Node version 8.12

https://github.com/nodejs/node/releases/tag/v8.12.0

Licensing

I believe that I took CC license from somewhere on nodejs.org. Does this license fits well for Browserslist and other libraries and software which use node-releases/browserslist? I'm not an expert in this.

cc @ai

Missing 10.20.0 and 12.16.2 releases from this week

FYI, while the sync and publish is still manual, it looks like these haven't been pushed here yet

Add a JavaScript module for easier access to data

While looking to implement this for nodejs/i18n, I found myself looking at what Browserlist was doing, and re-implementing it.
EX:

const schedule = require(node-releases).schedule // expose the release-schedule.json object
const nodejs = require(node-releases).nodejs// expose the release-schedule.json object

Other useful functions would be to have the functions to just return active releases

cannot install on npm

npm install --save node-releases ,then throw the error

Version 2.0

I want to release a new major version of node-releases with data/raw removed as it's never used by other packages as noted in #27. One thing I want to add to data/processed is v8 version as it would be useful to compare Node.js and v8 versions (for possible future https://github.com/kangax/compat-table update). As far as I understand, modules field is a Node ABI version which could be useful too. Not sure if we need security field. Does someone rely on it? Please let me know if some of these changes may affect you!

LICENSE file

Hello :)

Could you please add a LICENSE file to the project?

Publish version for node 16.13 LTS

Is there a chance to cut a new version that includes node 16.13 LTS 🙇

Release 2.0.6 not available through npmjs registry

I see [email protected] was published today, within the last hour:

While this version is visible on the package's page on npmjs.com, it seems that it can't be downloaded:

The package @types/eslint had a similar issue last week, which I believe turned out to be an npmjs problem ultimately. But while that package was clearly missing the README and other files, this one is not.

Does anyone know what's going on with version 2.0.6 on npmjs.com?

EDIT: it looks like the README is missing. The package's page on http://npmjs.com seems to be empty: