Skip to content

Add new ESP partner: NodeSource #8226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 15, 2025
+15 −6
Merged

Add new ESP partner: NodeSource #8226

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
11113c9
wip: add new ESP partner
bmuenzenmeyer Oct 14, 2025
836dc70
add copy from marketing
bmuenzenmeyer Oct 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions apps/site/pages/en/about/eol.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Major versions of Node.js are released, patched, and designated End-Of-Life on a
<span>Upgrade to the latest LTS Node.js®</span>
</Button>
<span>or</span>
<Button as="a" kind="warning" href="/esp/herodevs" className="flex-1">
<Button as="a" kind="warning" href="#commercial-support" className="flex-1">
<span>Get security support for EOL versions</span>
</Button>
</div>
Expand All @@ -37,8 +37,10 @@ When a version reaches End-Of-Life, it means that it will no longer receive upda

## Commercial Support

Despite the obvious downsides of using EOL releases, in practice, organizations face constraints that prevent immediate upgrades, such as legacy codebases, compliance requirements, or complex dependency chains. For users who cannot upgrade immediately but needs continued security support for End-Of-Life versions of Node.js, commercial support is available through the [OpenJS Ecosystem Sustainability Program](https://openjsf.org/blog/ecosystem-sustainability-program) partnership.
Despite the obvious downsides of using EOL releases, in practice, organizations face constraints that prevent immediate upgrades, such as legacy codebases, compliance requirements, or complex dependency chains. Through the [OpenJS Foundation Ecosystem Sustainability Program](https://openjsf.org/blog/ecosystem-sustainability-program), Node.js is supported by HeroDevs and NodeSource to provide commercial services for security fixes.

Node.js currently partners with HeroDevs to provide Never-Ending Support (NES) 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. For more detailed information, visit the [**HeroDevs Node.js NES page**](https://nodejs.org/esp/herodevs).
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.

Using EOL releases through NES should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.
NodeSource provides [security support](https://nodesource.com/services/support) for running older, unsupported versions of Node.js, giving teams more time and flexibility to transition to newer releases while maintaining a secure posture.

Using EOL releases through commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.
2 changes: 1 addition & 1 deletion apps/site/pages/en/about/partners.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ The program provides access to security patches, compliance assistance, and tech
to help bridge the gap while you plan your upgrade strategy. For more information about
End-Of-Life versions, please visit [End-Of-Life Node.js Releases](/about/eol)

> Using EOL releases through NES should be viewed as a temporary solution, the goal should always
> Using EOL releases through commercial support should be viewed as a temporary solution, the goal should always
> be to upgrade to actively supported versions.

<PartnersLogoList categories="esp" maxLength={null} sort="name" />
Expand Down
7 changes: 7 additions & 0 deletions apps/site/public/static/partners/constants.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,5 +33,12 @@
"href": "https://microsoft.com",
"categories": ["infrastructure"],
"weight": 2
},
{
"id": "NODESOURCE",
"name": "NodeSource",
"href": "https://nodesource.com/",
"weight": 3,
"categories": ["security", "esp", "release"]
}
]
2 changes: 1 addition & 1 deletion packages/i18n/src/locales/en.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@
"ltsVersionFeaturesNotice": "Want new features sooner? Get the <link>latest Node.js version</link> instead and try the latest improvements!"
},
"eolAlert": {
"message": "Commercial support for versions past the Maintenance LTS phase is available through our <link>OpenJS Ecosystem Sustainability Program partner HeroDevs</link>"
"message": "Commercial support for versions past the Maintenance LTS phase is available through our <link>OpenJS Ecosystem Sustainability Program partners</link>"
},
"eolChip": {
"severity": {
Expand Down
Loading