node-releases 2.0.56: json

Clean-room public code sample — generation instructions

Write a brand-new, minimal, self-contained code sample in this clean-room directory.
Do not copy, paraphrase, or reference any existing project source. Work only from this spec.

A csx.json manifest scaffold already exists. Do not recreate it from memory. Preserve its case.goal, packages and symbols; fill its empty case.contract with exact assertions and correct its environment, commands and verifierAdapter for the files you generate.

Goal: verify node-releases.json in pkg:npm/node-releases@2.0.56
Kind: HOW

Use EXACTLY these public packages and versions:
  - pkg:npm/node-releases@2.0.56
Demonstrate these symbols/APIs:
  - node-releases.json

Rules:
  - One focused purpose; the smallest project that proves the goal.
  - Include a contract test (test/contract.*) that runs OFFLINE and exits 0 exactly when the goal behavior works.
  - Pin every dependency with a lockfile so resolution is reproducible.
  - No secrets, credentials, or tokens. No real URLs (only example.com or localhost). No absolute paths.
  - No personal names, emails, company names, or project identifiers of any kind.
  - No binaries and no generated output (node_modules, dist, target, venv, .git, .env).
  - Keep it under 200 files and 256KB packed.

{"case":{"caseId":"case:sha256:52702a09af6987ee2455e2d153bc6ea325adfdd33e4fac78c06011e7971e311a","contract":["bare import of node-releases directly or non-existent root node-releases.json rejects with ERR_MODULE_NOT_FOUND","importing node-releases/data/processed/envs.json with type json yields an array of Node release records containing version, date, and LTS status","importing node-releases/data/release-schedule/release-schedule.json with type json yields major release lifecycle schedules containing start, lts, and end dates","CommonJS require can synchronously load both processed envs.json and release-schedule.json from node-releases","release metadata in envs.json accurately reflects LTS codenames such as Iron for Node 20 and Jod for Node 22 with boolean security flags"],"goal":"verify node-releases.json in pkg:npm/node-releases@2.0.56","kind":"HOW","packages":["pkg:npm/node-releases@2.0.56"],"schemaVersion":1,"symbols":["node-releases.json"]},"contractCommand":["node","test/contract.mjs"],"environment":{"arch":"x64","distro":"ubuntu","ecosystem":"npm","executionContext":"node","language":"javascript","libc":"glibc","libcVersion":"2.39","moduleSystem":"esm","os":"linux","osVersionBucket":"24","packageManager":"npm","runtime":"node","schemaVersion":1},"license":"MIT-0","packages":["pkg:npm/node-releases@2.0.56"],"schemaVersion":1,"subject":"pkg:npm/node-releases@2.0.56","symbols":["node-releases.json"],"verifierAdapter":"node-typescript@1"}

{
  "name": "sample-node-releases-json",
  "version": "1.0.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "sample-node-releases-json",
      "version": "1.0.0",
      "dependencies": {
        "node-releases": "2.0.56"
      }
    },
    "node_modules/node-releases": {
      "version": "2.0.56",
      "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.56.tgz",
      "integrity": "sha512-x0InOIyzgdk+eyaWaRJFH5snEtiImgBgblZ2CyPrLmqqcuMQkEvcDPHbzqbD8eDsSeJbVOjn+crzyzHaM4D+/A==",
      "license": "MIT",
      "engines": {
        "node": ">=18"
      }
    }
  }
}

{
  "name": "sample-node-releases-json",
  "version": "1.0.0",
  "type": "module",
  "private": true,
  "dependencies": {
    "node-releases": "2.0.56"
  }
}

{
  "schemaVersion": 1,
  "goal": "verify node-releases.json in pkg:npm/node-releases@2.0.56",
  "kind": "HOW",
  "packages": [
    "pkg:npm/node-releases@2.0.56"
  ],
  "symbols": [
    "node-releases.json"
  ]
}

import assert from 'node:assert/strict';
import { createRequire } from 'node:module';
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' };

// 1. bare import of node-releases directly or non-existent root node-releases.json rejects with ERR_MODULE_NOT_FOUND
await assert.rejects(
  () => import('node-releases'),
  (err) => err.code === 'ERR_MODULE_NOT_FOUND' || err.code === 'MODULE_NOT_FOUND'
);
await assert.rejects(
  () => import('node-releases/node-releases.json', { with: { type: 'json' } }),
  (err) => err.code === 'ERR_MODULE_NOT_FOUND' || err.code === 'MODULE_NOT_FOUND'
);

// 2. importing node-releases/data/processed/envs.json with type json yields an array of Node release records containing version, date, and LTS status
assert.ok(Array.isArray(envs), 'envs must be an array');
assert.ok(envs.length > 300, 'envs array must have over 300 releases');
for (const entry of envs.slice(0, 20)) {
  assert.equal(entry.name, 'nodejs');
  assert.equal(typeof entry.version, 'string');
  assert.equal(typeof entry.date, 'string');
  assert.ok(typeof entry.lts === 'string' || entry.lts === false);
  assert.equal(typeof entry.security, 'boolean');
  assert.equal(typeof entry.v8, 'string');
}

// 3. importing node-releases/data/release-schedule/release-schedule.json with type json yields major release lifecycle schedules containing start, lts, and end dates
assert.ok(typeof schedule === 'object' && schedule !== null && !Array.isArray(schedule));
assert.ok('v20' in schedule, 'schedule contains v20');
assert.ok('v22' in schedule, 'schedule contains v22');
assert.match(schedule['v20'].start, /^\d{4}-\d{2}-\d{2}$/);
assert.match(schedule['v20'].end, /^\d{4}-\d{2}-\d{2}$/);
assert.equal(schedule['v22'].codename, 'Jod');
assert.match(schedule['v22'].start, /^2024-/);
assert.match(schedule['v22'].lts, /^2024-/);
assert.match(schedule['v22'].maintenance, /^2025-/);
assert.match(schedule['v22'].end, /^2027-/);

// 4. CommonJS require can synchronously load both processed envs.json and release-schedule.json from node-releases
const require = createRequire(import.meta.url);
const cjsEnvs = require('node-releases/data/processed/envs.json');
const cjsSchedule = require('node-releases/data/release-schedule/release-schedule.json');
assert.equal(cjsEnvs.length, envs.length);
assert.equal(cjsSchedule['v22'].codename, 'Jod');

// 5. release metadata in envs.json accurately reflects LTS codenames such as Iron for Node 20 and Jod for Node 22 with boolean security flags
const v20Lts = envs.find((e) => e.version.startsWith('20.') && e.lts);
assert.ok(v20Lts, 'Node 20 LTS release entry found');
assert.equal(v20Lts.lts, 'Iron');

const v22Lts = envs.find((e) => e.version.startsWith('22.') && e.lts);
assert.ok(v22Lts, 'Node 22 LTS release entry found');
assert.equal(v22Lts.lts, 'Jod');

const secReleases = envs.filter((e) => e.security === true);
assert.ok(secReleases.length > 0);
assert.ok(secReleases.every((e) => e.security === true));