MCPcopy Index your code
hub / github.com/chicoxyzzy/node-releases

github.com/chicoxyzzy/node-releases @v2.0.50

Chat with this repo
repository ↗ · DeepWiki ↗ · release v2.0.50 ↗ · + Follow
1 symbols 4 edges 1 files 0 documented · 0% 2 cross-repo links
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

Node.js releases data

npm version License: MIT

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

Usage

// CommonJS
const envs = require('node-releases/data/processed/envs.json');
const schedule = require('node-releases/data/release-schedule/release-schedule.json');

// ESM (Node.js 22+)
import envs from 'node-releases/data/processed/envs.json' with { type: 'json' };
import schedule from 'node-releases/data/release-schedule/release-schedule.json' with { type: 'json' };

Releases

Releases are published automatically by a nightly GitHub Actions workflow whenever upstream Node.js release data changes. Publishing uses npm trusted publishing (OIDC, no long-lived tokens) and ships provenance attestations.

Core symbols most depended-on inside this repo

writeJSON
called by 2
scripts/build.js

Shape

Function 1

Languages

TypeScript100%

Modules by API surface

scripts/build.js1 symbols

Used by 2 indexed graphs manifest dependencies, hub-wide

For agents

$ claude mcp add node-releases \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact