node-releases 2.0.53

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 pkg:npm/node-releases@2.0.53
Kind: HOW

Use EXACTLY these public packages and versions:
  - pkg:npm/node-releases@2.0.53
Constraints:
  - executionContext: node
Required runtime conditions:
  - ecosystem: npm
  - language: javascript
  - moduleSystem: cjs
  - packageManager: npm@10.9.8
  - runtime: node@22.23.2

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:aca32c54c031bc08624f9b9e9256c87ada0ee97a43f54a6d3ae36e9f805cc00c","constraints":{"executionContext":"node"},"contract":["bare import or require of node-releases fails with ERR_MODULE_NOT_FOUND or MODULE_NOT_FOUND because no root entrypoint is exported","importing node-releases/data/processed/envs.json provides an array of release records with version, date, lts, security, and v8 metadata","envs.json records include LTS releases such as v20 and v22 with active LTS codename strings or false for non-LTS releases","envs.json correctly flags security release versions as boolean","importing node-releases/data/release-schedule/release-schedule.json provides release timelines with start and end dates for major versions","release-schedule.json defines LTS lifecycle timestamps including start, lts, maintenance, end, and codename for even-numbered release branches"],"goal":"verify pkg:npm/node-releases@2.0.53","kind":"HOW","packages":["pkg:npm/node-releases@2.0.53"],"schemaVersion":1},"contractCommand":["node","test/contract.mjs"],"environment":{"arch":"x64","distro":"ubuntu","ecosystem":"npm","executionContext":"node","language":"javascript","libc":"glibc","libcVersion":"2.39","moduleSystem":"cjs","os":"linux","osVersionBucket":"24","packageManager":"npm","packageManagerVersion":"10.9.8","runtime":"node","runtimeVersion":"22.23.2","schemaVersion":1},"license":"MIT-0","packages":["pkg:npm/node-releases@2.0.53"],"schemaVersion":1,"subject":"pkg:npm/node-releases@2.0.53","verifierAdapter":"node-typescript@1"}

{
  "name": "sample-node-releases",
  "version": "1.0.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "sample-node-releases",
      "version": "1.0.0",
      "dependencies": {
        "node-releases": "2.0.53"
      }
    },
    "node_modules/node-releases": {
      "version": "2.0.53",
      "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.53.tgz",
      "integrity": "sha512-D9UOmYG3UH1V+ENW56t5QXBwJw1YEY18ruVeus89Rw+SyIgjPkCO84bRzO3uNIYosJbNwiabWVn48o3uJLjxFQ==",
      "license": "MIT",
      "engines": {
        "node": ">=18"
      }
    }
  }
}

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

{
  "schemaVersion": 1,
  "goal": "verify pkg:npm/node-releases@2.0.53",
  "kind": "HOW",
  "packages": [
    "pkg:npm/node-releases@2.0.53"
  ],
  "constraints": {
    "executionContext": "node"
  },
  "runtimeConditions": {
    "ecosystem": "npm",
    "language": "javascript",
    "moduleSystem": "cjs",
    "packageManager": "npm@10.9.8",
    "runtime": "node@22.23.2"
  }
}

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 or require of node-releases fails with ERR_MODULE_NOT_FOUND or MODULE_NOT_FOUND because no root entrypoint is exported
await assert.rejects(
  () => import('node-releases'),
  (err) => err.code === 'ERR_MODULE_NOT_FOUND' || err.code === 'MODULE_NOT_FOUND'
);

const require = createRequire(import.meta.url);
assert.throws(
  () => require('node-releases'),
  (err) => err.code === 'MODULE_NOT_FOUND'
);

// 2. importing node-releases/data/processed/envs.json provides an array of release records with version, date, lts, security, and v8 metadata
assert.ok(Array.isArray(envs));
assert.ok(envs.length > 300);
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. envs.json records include LTS releases such as v20 and v22 with active LTS codename strings or false for non-LTS releases
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 nonLts = envs.find((e) => e.lts === false);
assert.ok(nonLts);
assert.equal(nonLts.lts, false);

// 4. envs.json correctly flags security release versions as boolean
const secReleases = envs.filter((e) => e.security === true);
assert.ok(secReleases.length > 0);
assert.ok(secReleases.every((e) => e.security === true));

// 5. importing node-releases/data/release-schedule/release-schedule.json provides release timelines with start and end dates for major versions
assert.ok(typeof schedule === 'object' && schedule !== null && !Array.isArray(schedule));
assert.ok('v20' in schedule);
assert.ok('v22' in schedule);
assert.match(schedule['v20'].start, /^\d{4}-\d{2}-\d{2}$/);
assert.match(schedule['v20'].end, /^\d{4}-\d{2}-\d{2}$/);

// 6. release-schedule.json defines LTS lifecycle timestamps including start, lts, maintenance, end, and codename for even-numbered release branches
const sched22 = schedule['v22'];
assert.equal(sched22.codename, 'Jod');
assert.match(sched22.start, /^2024-/);
assert.match(sched22.lts, /^2024-/);
assert.match(sched22.maintenance, /^2025-/);
assert.match(sched22.end, /^2027-/);