blog: add Migrating from Node.js 22 to Node.js 24

[richardlau]

Description

Summarize breaking and important changes when migrating from Node.js 22 LTS to Node.js 24 LTS.

I've created a new blog post for this (in announcements as that's where we put, e.g. https://nodejs.org/en/blog/announcements/v5-to-v7 (which is not quite the same)). My reasoning for a separate post to the normal release post is that it would be:

• Easier to correct/update.
• Not everyone using Node.js 24 LTS will be migrating from 22 (e.g. some might be new to Node.js, or be upgrading from an even earlier version).
• Visibility.

---

Setting blocked -- this should land at the same time as (or shortly after) Node.js 24.11.0 which will be the LTS transition release. I would rather land with the release (with no obvious errors) and then allow edits to this afterwards for any improvements.

Validation

New page is created.

Related Issues

Refs: nodejs/Release#716

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
nodejs-org	Ready	Preview	Oct 27, 2025 4:37pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.52%. Comparing base (e14424a) to head (cd57456).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8270      +/-   ##
==========================================
- Coverage   76.56%   76.52%   -0.05%     
==========================================
  Files         117      117              
  Lines        9733     9733              
  Branches      329      330       +1     
==========================================
- Hits         7452     7448       -4     
- Misses       2279     2283       +4     
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bmuenzenmeyer]

I think there is a typo in the typo fix message 🙃

[AugustinMauroy]

what should be link with potential future migrations sections?

https://github.com/nodejs/nodejs.org/pull/8053/files#diff-48b48b39d53193bb47f38c0f11972ba813cc81d41c15dcd137eca26968eb3892

[richardlau]

what should be link with potential future migrations sections?

https://github.com/nodejs/nodejs.org/pull/8053/files#diff-48b48b39d53193bb47f38c0f11972ba813cc81d41c15dcd137eca26968eb3892

Please suggest the update you want to see. It will always be possible to update the post after it lands. If your point is that the link to https://nodejs.org/en/learn/migrations/introduction will go away with #8053, it could be updated as part of that?

[AugustinMauroy]

what should be link with potential future migrations sections?
https://github.com/nodejs/nodejs.org/pull/8053/files#diff-48b48b39d53193bb47f38c0f11972ba813cc81d41c15dcd137eca26968eb3892

Please suggest the update you want to see. It will always be possible to update the post after it lands. If your point is that the link to https://nodejs.org/en/learn/migrations/introduction will go away with #8053, it could be updated as part of that?

The pr that I linked is a pr that remove learn subsection about userland migration to include the userland migration explain on getting started. AND add migration guide on blog subsection.

So IMO we shouldn't do an announcement blog post for migrations. We should just merge the pr with migrations guide. and on LTS annonce link the migration guides.

[richardlau]

what should be link with potential future migrations sections?
https://github.com/nodejs/nodejs.org/pull/8053/files#diff-48b48b39d53193bb47f38c0f11972ba813cc81d41c15dcd137eca26968eb3892

Please suggest the update you want to see. It will always be possible to update the post after it lands. If your point is that the link to https://nodejs.org/en/learn/migrations/introduction will go away with #8053, it could be updated as part of that?

The pr that I linked is a pr that remove learn subsection about userland migration to include the userland migration explain on getting started. AND add migration guide on blog subsection.

So IMO we shouldn't do an announcement blog post for migrations. We should just merge the pr with migrations guide. and on LTS annonce link the migration guides.

If you read what I've put together for this PR, it's more than just "here is a list of codemods for migrations". See for example,

• The section on platforms that are no longer supported.
• The section on OpenSSL 3.5.

If you want to take what is here and merge it into the other PR, feel free.

[AugustinMauroy]

If you want to take what is here and merge it into the other PR, feel free.

That a good thing. Because I'm now 100% aware of all thing that change between two LTS

[RafaelGSS]

This is amazing. Thanks!

[richardlau]

I have removed the blocked label, since Node.js 24.11.0 has been promoted (see also #8280). However as noted above this might get subsumed into #8053 -- I'll leave that decision to the website team.

[avivkeller]

@AugustinMauroy are you still blocking?

[AugustinMauroy]

I don't totally block, but I think we should try to move the entire migration section instead of having an announcement post. Which will either be removed or overwritten.