ns-node-upgrade

Plans Node.js runtime upgrades with live LTS/EOL data, dependency checks, and rollback guidance.

6|7|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/nodesource/nsolid-plugin --skill ns-node-upgrade-nodesource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ns-node-upgrade
Source: https://github.com/nodesource/nsolid-plugin/tree/main/skills/ns-node-upgrade
Command: npx skills add https://github.com/nodesource/nsolid-plugin --skill ns-node-upgrade-nodesource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Upgrading a project's Node.js runtime is risky without knowing which release lines are still supported, which dependencies break on newer versions, and what files need updating. This Skill produces a complete, evidence-based upgrade plan so you avoid landing on an EOL version or breaking CI. ## Core Features & Use Cases - Live Release Schedule: Fetches the authoritative Node.js LTS/EOL table from endoflife.date (with an offline fallback) so recommendations never rely on stale training data. - Automatic Version Detection: Reads the current version from package.json engines, .nvmrc, .node-version, or the runtime on PATH, treating project pins as authoritative. - Full Upgrade Guide: Delivers a recommended target version, key changes, step-by-step migration (nvmrc, engines, CI/CD, Docker), dependency compatibility checks via NCM, and verification steps. - Use Case: Your project pins Node 16 in .nvmrc and CI is failing deprecation checks. Ask for an upgrade plan and receive a recommendation for the newest Active LTS, the exact files to change, and how to verify the migration. ## Quick Start Ask the assistant to plan a Node.js upgrade for this project and recommend which LTS version to move to.

Frequently Asked Questions about ns-node-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Node.js version in my project?▼

Detect the current version from package.json engines, .nvmrc, or .node-version, then update those pins to the target LTS, run nvm install and nvm use, update CI and Docker images, and run your test suite watching for deprecation warnings.

Which Node.js LTS version should I upgrade to?▼

Upgrade to the newest Active LTS line if your current version is EOL or within six months of EOL. The skill fetches the live release schedule from endoflife.date so the recommendation reflects current support dates, never an already-EOL line.

How do I check dependency compatibility with a new Node version?▼

Read direct dependencies from package.json and pass name/version pairs to the NCM getPackageVersions tool, which reports known incompatibilities with the target Node version. Native modules may also need a node-gyp rebuild.

Does the Node version detection work without running node --version?▼

Yes. Detection checks package.json engines first, then .nvmrc and .node-version files, only falling back to node --version for the runtime on PATH. Project-pinned versions are treated as authoritative over the PATH runtime.

What happens if the live Node.js release schedule cannot be fetched?▼

The fetch script falls back to an embedded snapshot of release data and prints a warning. If neither live data nor an injected table is available, the skill states that release data could not be verified and labels any fallback as potentially stale.