You can continue to run older versions of nodejs and NPM just fine. Once they are installed, they don't require any other outside resources in order to run. They run locally using only local resources. And, older versions of nodejs or NPM can still be installed somewhere new if desired/required.

An older version of nodejs or NPM will not just stop running because it's no longer supported. There's no outside dependency that tells it to stop running when it reaches end of life. If you noticed something like that happening, then it is probably just a coincidence and something else changed in your system or configuration that caused it to stop working properly.

Now, there are plenty of issues with running older versions of nodejs that you have to be aware of.

  1. You don't get security updates.
  2. You don't get updates to adapt to OS changes.
  3. You don't get bug fixes.
  4. The current versions of NPM modules you are using may no longer support your specific nodejs version or a more modern OS version. You can, of course, continue to run older versions of modules too, if desired to maintain compatibility with your older version of nodejs, but those older modules will have the same possible issues mentioned here as an older version of nodejs.

To me, the biggest risk with holding on to an older version of nodejs is that at some point a serious security risk will be found and you will HAVE to do something about it. With no official support for that security fix in an older version of nodejs, you will have to either manually fix the security vulnerability yourself in your current version of nodejs, change your code in some way to protect against it or upgrade to a newer version of nodejs that contains the desired security fix. The longer you wait to do this, the more potential issues you may find in bringing your software up-to-date.

In my book, it's better to continually move your software forward with supported versions of nodejs. You don't have to do it frequently and you don't have to run on the latest/greatest version, but there are significant benefits to always running an LTS version.

Answer from jfriend00 on Stack Overflow
🌐
endoflife.date
endoflife.date › nodejs
Node.js | endoflife.date
6 days ago - After six months, odd-numbered ... support”, which typically guarantees that critical bugs will be fixed for a total of 30 months....
Microsoft Office
Check end-of-life, release policy and support schedule for Microsoft Office.
Firefox
Check end-of-life, release policy and support schedule for Firefox.
Ansible
Check end-of-life, release policy and support schedule for Ansible.
Docker Engine
Check end-of-life, release policy and support schedule for Docker Engine.
🌐
HeroDevs
herodevs.com › blog-posts › node-js-end-of-life-dates-you-should-be-aware-of
HeroDevs Blog | Node.js End-of-Life Dates You Should Be Aware Of
End-of-life: April 30, 2025 · Node.js 20.x · End of Active LTS: October 13, 2024 · End of Maintenance LTS: April 30, 2026 · End-of-life: April 30, 2026 · Node.js 22.x · End of Active LTS: October 21, 2025 · End of Maintenance LTS: April ...
🌐
GitHub
github.blog › home › changelogs › deprecation of node 20 on github actions runners
Deprecation of Node 20 on GitHub Actions runners - GitHub Changelog
September 19, 2025 - Node20 will reach end-of-life (EOL) in April of 2026. As a result we have started the deprecation process of Node20 for GitHub Actions.
🌐
Node.js
nodejs.org › en › about › eol
Node.js — End-Of-Life
View the Node.js release schedule. When a version reaches End-Of-Life, it means that it will no longer receive updates, including security patches.
🌐
Node.js
nodejs.org › en › about › previous-releases
Node.js — Node.js Releases
After six months, odd-numbered ... support", which typically guarantees that critical bugs will be fixed for a total of 30 months....
🌐
Medium
medium.com › @Games24x7Tech › node-js-v20-upgrade-guide-best-practices-and-performance-insights-f76d7ace09ff
Node.js v20 upgrade guide: Best Practices and Performance Insights | by Games24x7 Blogs | Medium
September 6, 2024 - Node.js v20 upgrade guide: Best Practices and Performance Insights As of April 2023, Node.js versions less than v16 have reached their end of life, marking an essential milestone for developers and …
Top answer
1 of 1
5

You can continue to run older versions of nodejs and NPM just fine. Once they are installed, they don't require any other outside resources in order to run. They run locally using only local resources. And, older versions of nodejs or NPM can still be installed somewhere new if desired/required.

An older version of nodejs or NPM will not just stop running because it's no longer supported. There's no outside dependency that tells it to stop running when it reaches end of life. If you noticed something like that happening, then it is probably just a coincidence and something else changed in your system or configuration that caused it to stop working properly.

Now, there are plenty of issues with running older versions of nodejs that you have to be aware of.

  1. You don't get security updates.
  2. You don't get updates to adapt to OS changes.
  3. You don't get bug fixes.
  4. The current versions of NPM modules you are using may no longer support your specific nodejs version or a more modern OS version. You can, of course, continue to run older versions of modules too, if desired to maintain compatibility with your older version of nodejs, but those older modules will have the same possible issues mentioned here as an older version of nodejs.

To me, the biggest risk with holding on to an older version of nodejs is that at some point a serious security risk will be found and you will HAVE to do something about it. With no official support for that security fix in an older version of nodejs, you will have to either manually fix the security vulnerability yourself in your current version of nodejs, change your code in some way to protect against it or upgrade to a newer version of nodejs that contains the desired security fix. The longer you wait to do this, the more potential issues you may find in bringing your software up-to-date.

In my book, it's better to continually move your software forward with supported versions of nodejs. You don't have to do it frequently and you don't have to run on the latest/greatest version, but there are significant benefits to always running an LTS version.

🌐
Redis
versionlog.com › nodejs › 20
Node.js 20: List Releases, Release Date, End of Life
Key updates include changes to ... for web standards. Node.js 20 enters Long Term Support with active maintenance until April 2026, making it a solid choice for production apps....
🌐
GitHub
github.com › nodejs › Release
GitHub - nodejs/Release: Node.js Release Working Group
Following those 12 months of active support, the major version will transition into "maintenance" mode for 18 months. Prior to Node.js 12, the active period was 18 months and the maintenance period 12 months.
Starred by 4.2K users
Forked by 629 users
Languages   JavaScript
Find elsewhere
🌐
End of Life
endoflife.software › programming-languages › server-side-scripting › nodejs
EOL Node.js | End of Life (EOL) | OpenJS Foundation | Lifecycle
OpenJS Foundation Node.js product lifecycle information. Get end of life (EOL) and release dates for all releases of programming language Node.js
🌐
Redis
versionlog.com › nodejs
Node.js: All Releases, End of Life, Release Date
List releases of Node.js, end of life, end of support, support status, release date of each version, LTS versions. Node.js is an open-source, JavaScript...
🌐
GitHub
github.com › SharePoint › sp-dev-docs › issues › 10151
Node.js 20 Support (18 reaches end-of-life on April 30, 2025) · Issue #10151 · SharePoint/sp-dev-docs
January 24, 2025 - Node.js 20 Support (18 reaches end-of-life on April 30, 2025)#10151 · Copy link · Assignees ·
Published   Mar 12, 2025
🌐
Node.js
nodejs.org › en › blog › release › v20.9.0
Node.js — Node.js v20.9.0 (LTS)
This release marks the transition ... October 2024. After that time, it will move into "Maintenance" until end of life in April 2026....
🌐
Itechtics
itechtics.com › eol › node.js
Node.js Lifecycle: End Of Life And Support Status
Version · Released · Active Support · Security Support · Node.js 24 · 6 months and 4 weeks ago (6 May 2025) Ends in 10 months and 2 weeks (20 October 2026) Ends in 2 years and 4 months (30 April 2028) Node.js 23 ·
🌐
Node.js
nodejs.org › en › blog › announcements › node-18-eol-support
Node.js — Beware of End-of-Life Node.js Versions - Upgrade or Seek Post-EOL Support
The security implications are immediate and serious. The May 2025 security releases revealed that Node.js 20 is vulnerable to 1 low severity issue, 1 high severity issue, and 1 medium severity issue.
🌐
AWS
aws.amazon.com › blogs › devops › announcing-the-end-of-support-for-node-js-18-x-in-aws-cdk
Announcing the end of support for Node.js 18.x in AWS CDK | AWS DevOps & Developer Productivity Blog
July 15, 2025 - Beginning December 1st, 2025, AWS CDK will officially discontinue support for Node.js 18.x across all components and ecosystem projects. From this point forward, all bug fixes, security patches, and new feature development will target only supported ...
🌐
GitHub
github.com › awslabs › landing-zone-accelerator-on-aws › issues › 961
Addressing AWS Lambda Node.js 20.x end-of-life · Issue #961 · awslabs/landing-zone-accelerator-on-aws
1 month ago - Starting on April 30, 2026, Lambda will no longer apply security patches and other updates to the Node.js 20.x runtime used by Lambda functions, and functions using Node.js 20.x will no longer be e...
Published   Nov 18, 2025