Yes, Node.js 22 is still supported. It entered Maintenance LTS on 21 October 2025 and the Node.js release schedule lists 30 April 2027 as its end of life. In Maintenance, only critical bug and security fixes ship. Plan to move before spring 2027.
Where line 22 sits
| Milestone | Date |
|---|---|
| Initial release | 2024-04-24 |
| Active LTS began | 2024-10-29 |
| Maintenance began | 2025-10-21 |
| End of life | 2027-04-30 |
Source: the Node.js Release working group schedule file. The latest 22.x patch shown by a third party tracker, endoflife.date, was 22.23.3 when I checked, which is a reminder that patches keep arriving while a line is supported.
What Maintenance changes for you
Maintenance is not a warning light, but it does change the incentives. New language and runtime features land on newer lines. Dependency authors begin to drop the older line from their test matrix. Over the last six months of a line's life you may find a package whose newest release asks for a newer Node.js.
You can see that early. Run your install with the strict engines setting turned on. The npm documentation says the engines field is advisory only unless engine-strict is set, so a normal install may only print a warning that is easy to miss.
A move plan in five steps
- Pick the target. Line 24 is in Active LTS until 20 October 2026 and then Maintenance. Line 26 is scheduled for Active LTS on 28 October 2026. Choose based on how long you want to stay put.
- Change the version in one place. Update the base image tag, the CI setup step and any
enginesentry together, so local, CI and production agree. - Run the full test suite twice. Once with the new line and your existing lockfile, once after refreshing dependencies. The first run isolates runtime changes from package changes.
- Check native modules. Anything compiled for a specific Node.js ABI must be rebuilt. Watch install logs for rebuild failures.
- Canary, then promote. Send a slice of traffic to the new line, watch error rates and memory, then widen.
Keep the previous image tag available for a rollback window.
Try it yourself
The continuous monitoring demo shows how findings change over time on a project. After a runtime move, this is the view you want, so you can confirm that old findings closed and no new ones opened.
Click through it at your own pace, or open it full screen.
Safeguard supports dependency scanning and continuous monitoring, so you can see what changed after a runtime or package upgrade. The free scan is at gold.safeguard.sh/scan.
Quick check
Do I get security fixes for Node.js 22 until 30 April 2027?
The schedule lists that date as end of life, so fixes are expected until then. In Maintenance they are limited to critical issues.
Should I skip 24 and go to 26?
It is a valid choice if you can wait until 26 enters Active LTS on 28 October 2026. Either way, test on the line you pick before you commit.
Sources
- Node.js Release working group schedule file
- Node.js releases
- endoflife.date Node.js data
- npm package.json documentation
Last reviewed: 19 October 2026.
