What's Changed
- fix: support node 22 by @serhalp in #39349
- fix(gatsby): update socket.io to address vulnerable subdeps by @serhalp in #39352
Node.js 22
This release formally introduces Node.js 22 support, which is officially tested and supported going forward.
If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.
⚠️ Known Issue: gatsby develop fails with Node.js 22.7.0, 22.8.0, and 22.9.0
There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes gatsby develop to fail with the error reported in #39068.
👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)
⚠️ Known Issue: Page loads may hang in dev with experimental DEV_SSR enabled and Node.js ≥22.14.0 (or ≥20.19.0)
This will not affect most users.
A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the gatsby develop dev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimental DEV_SSR flag.
👉🏼 To avoid this, disable the experimental DEV_SSR flag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)
New Contributors
Thank you!
- @pajosieg made their first contribution in #39169
- @johnmurphy01 made their first contribution in #39324
- @shrisoundharyaa made their first contribution in #39286
Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0