porro

End of life  /  Node.js

Release cycles

Node.js end of life

3 cycles are supported, 26 to 22. 22 gets security fixes until 30 Apr 2027. Active support means bug fixes and security fixes; after it, security fixes only.

  1. 26
  2. 25
  3. 24
  4. 23
  5. 22
  • Active support
  • Security fixes only
  • Supported
  • Ends within 90 days
  • Ended
26 LTS, supported until 30 Apr 2029 26.13.0 25 Ended until 1 Jun 2026 25.9.0 24 Security fixes only until 30 Apr 2028 24.22.2 23 Ended until 1 Jun 2025 23.11.1 22 Security fixes only until 30 Apr 2027 22.23.4 21 Ended until 1 Jun 2024 21.7.3 20 Ended until 30 Apr 2026 20.20.2 19 Ended until 1 Jun 2023 19.9.0 18 Ended until 30 Apr 2025 18.20.8 17 Ended until 1 Jun 2022 17.9.1 16 Ended until 11 Sep 2023 16.20.2 15 Ended until 1 Jun 2021 15.14.0 14 Ended until 30 Apr 2023 14.21.3 13 Ended until 1 Jun 2020 13.14.0 12 Ended until 30 Apr 2022 12.22.12 11 Ended until 30 Jun 2019 11.15.0 10 Ended until 30 Apr 2021 10.24.1 9 Ended until 30 Jun 2018 9.11.2 8 Ended until 31 Dec 2019 8.17.0 7 Ended until 30 Jun 2017 7.10.1 6 Ended until 30 Apr 2019 6.17.1 5 Ended until 30 Jun 2016 5.12.0 4 Ended until 30 Apr 2018 4.9.1 3 Ended until 15 Sep 2015 3.3.1 2 Ended until 28 Jul 2015 2.5.0 1 Ended until 9 Jul 2015 1.8.4

How to check your version

Which Node.js is this site on?

On the server

$ node -v
v22.11.0
# build servers and CI can run a different version

In the project

$ cat .nvmrc package.json | grep -A2 engines
# engines and .nvmrc say what you expect, not what runs

On Forge

Server → Node
Node version: 22
# set per server, used by deploy scripts

Know before support ends.

Porro reads the PHP, framework and database version from every site and tells you 90 days before support runs out.

Start your free trial →

Dates from endoflife.date/nodejs, checked daily · data as of 29 Oct 2026.