# Node.js 22 LTS — EOL Date, Support Timeline, and What Comes Next > Source: > Published: 2026-05-23 04:21:31+00:00 Node.js 22 became Active LTS in October 2024. That sounds recent. It isn't. Active LTS means the clock is already running. Node.js 22 reaches End of Life on April 30, 2027 — less than two years from now. And if the pattern from Node 16, 18, and 20 holds, a significant chunk of production environments will still be running it six months after that date. This article covers the full Node.js 22 support timeline, how it fits into the broader release schedule, what the EOL Risk Score looks like today versus in 2027, and what your team should be planning now. Node.js follows a predictable release cadence: even-numbered versions become LTS, odd-numbered versions don't. Node.js 22 is even, so it gets the full LTS treatment — Active LTS for two years, then Maintenance for six months, then EOL. The Maintenance phase is the one most teams miss. After October 2026, Node.js 22 only receives critical bug fixes and security patches — no new features, no non-critical fixes. If you're still on Node 22 in early 2027, you're already in a degraded support window before you even hit EOL. Here's the full picture as of May 2026: Node.js 20 just hit EOL on April 30, 2026 — less than a month ago. If your team is running Node 20 in production today, you're already in the same position teams were in with Node 18 a year ago. Node.js 22's current EOL Risk Score is 50 Medium — it's supported, but the attack surface score (30/30) is already baked in because Node.js is a high-exposure runtime regardless of support status. That score climbs to Critical the moment it hits EOL in April 2027. The EOL Risk Score™ on endoflife.ai breaks down like this for Node.js 22 today: The day Node.js 22 hits EOL on April 30, 2027, the Recency score jumps from 0 to 40. Total score: 90 Critical. Nothing about your infrastructure changes — just the date. That's the EOL cliff. Teams that plan migrations 6-12 months in advance avoid it. Teams that don't end up running Critical-rated software in production while scrambling to upgrade. Node.js 18 hit EOL on April 30, 2025. Based on download and deployment data, a significant portion of Node.js production workloads were still on Node 18 six months later. The same pattern played out with Node 16 and Node 14 before it. Why does this keep happening? The teams that handle this well aren't faster — they just start earlier. If you're reading this in May 2026, you have 23 months before Node 22 EOL. That's comfortable. If you're reading this in January 2027, you have 3 months. That's a fire drill. Before you start planning the migration to Node 24, know what you're on: node:test is production-readyrequire() for ES modules — experimental but significant for ecosystem compatibilityws dependency needed for basic use casesNode.js 22 is a genuinely good release. That's exactly why it'll still be running in production in 2028 at companies that didn't plan ahead. If you're on Node 18 or 20: You're already past EOL or just hit it. This is urgent. Check your EOL Risk Score at endoflife.ai/nodejs/18 or endoflife.ai/nodejs/20. If you're on Node 22: You have runway. Use it. Schedule the Node 24 migration for Q1 2027 at the latest — that gives you a 3-month buffer before EOL and keeps you out of the Maintenance-only window. If you're on Node 24: You're current. Node 24 EOL is April 2028. Check back in 18 months. Scan your full stack: Node version is one data point. The underlying OS, runtime dependencies, and framework versions all have their own EOL dates. Use the Stack Scanner at endoflife.ai to get the full picture. Every Node.js version has a dedicated score card on endoflife.ai: EOL Risk Score™ is a proprietary methodology developed by endoflife.ai. Scores are calculated at build time from four factors: EOL Recency, Attack Surface, CISA KEV Exposure, and Extended Support Availability. Part of The EOL Intelligence Report series on DEV.to.