You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/site/pages/en/about/eol.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,8 @@ Despite the obvious downsides of using EOL releases, in practice, organizations
41
41
42
42
HeroDevs provides [Never-Ending Support (NES)](https://nodejs.org/esp/herodevs) for Node.js versions past their official maintenance phase. This includes security patches, compliance assistance, and technical support to help bridge the gap while you plan your upgrade strategy.
43
43
44
+
NodeSource offers commercial-grade upgrade assessments and expert support to safely modernize Node.js applications still running on EOL versions. Their guided [Upgrade Program](https://nodesource.com/products/nodejs-upgrade) delivers in-depth risk analysis, identifies migration blockers, and provides a custom roadmap to streamline your upgrade journey.
45
+
44
46
Using EOL releases through commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.
0 commit comments