Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
85
✓README✓License✓Contributing○Code of Conduct○Issue Template✓PR Template
Recent PRs & issues
Quiet · 2 discussions · Last activity 3mo ago
See all on GitHub →The Node.js release schedule is changing. The announcement is: https://nodejs-org-git-fork-ulisesgascon-release-announcement-openjs.vercel.app/en/blog/announcements/evolving-the-nodejs-release-schedule Old Node.js terminology (https://nodejs.org/en/about/previous-releases): even: current / active LTS / maintenance LTS odd: current / maintenance New terminology used in announcement: alpha / interim / LTS I think this makes the little used node support labels somewhat obsolete (like ), and is not mentioned. got used in some training material and will retain that as an alias even if do not document. Likewise, stable. Not sure if users will want to target the latest version _after_ it reaches alpha? uses the index information from https://github.com/nodejs/nodejs-dist-indexer and does not do date calculations. I am watching that repo to see if alpha/interim get added to the index.
Recent fixes
Problem Primary labels and aliases are: , , Until last week, was the newest version of node 24, which will be the next lts version. was (and is stillcurrentlatestactivecurrent25.0.0ltslts_activelts_latestsupported22.21.0labelnn latestn 24activecurrentlts_active2422` is now in maintenance. Image from Node.js Releases: !image Configuration Details
Structured data for AI agents
Repository: tj/n. Description: Node version management Stars: 19519, Forks: 763. Primary language: Shell. Languages: Shell (99.8%), Makefile (0.2%). License: MIT. Latest release: v10.2.0 (9mo ago). Open PRs: 0, open issues: 2. Last activity: 3mo ago. Community health: 85%. Top contributors: shadowspawn, tj, maxrimue, qw3rtman, troy0820, tjwebb, 73rhodes, PeterDaveHello, benatkin, jeromedecoster and others.