Skip to content
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

blog: ecosystem node 22 update blog #698

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

blog: ecosystem node 22 update blog #698

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
848fd83
docs: ecosystem node 22 update blog
VerteDinde Dec 2, 2024
8377e09
chore: apply suggestions from code review
VerteDinde Dec 2, 2024
b3100af
Update blog/node-22-ecosystem-update.md
erickzhao Dec 3, 2024
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
40 changes: 40 additions & 0 deletions blog/node-22-ecosystem-update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: Moving our Ecosystem to Node 22
date: 2024-12-02T00:00:00.000Z
authors: VerteDinde
slug: ecosystem-node-22
tags: [community, ecosystem]
---

In early 2025, Electron’s npm ecosystem repos (under the `@electron/` and `@electron-forge/` namespaces) will move to Node.js 22 as the minimum supported version.

---

In early 2025, Electron’s npm ecosystem repos (under the `@electron/` and `@electron-forge/` namespaces) will move to Node.js 22 as the minimum supported version.
VerteDinde marked this conversation as resolved.
Show resolved Hide resolved

### What does this mean?

In the past, packages in Electron’s npm ecosystem (Forge, Packager, etc) have supported Node versions for as long as possible, even after a version has reached its End-Of-Life (EOL) date. This is done to make sure we don’t fragment the ecosystem—we understand that many projects depend on older versions of Node, and we don’t want to risk stranding those projects unless there was a pressing reason to upgrade.

Over time, maintenance of this policy has become increasingly difficult for a few reasons:
erickzhao marked this conversation as resolved.
Show resolved Hide resolved

- Lack of official Node.js 14 macOS ARM64 builds requires us to maintain CI infrastructure workarounds to provide full test coverage.
- `engines` requirements for upstream package dependencies have moved forward, making it increasingly difficult to resolve supply chain security issues with dependency bumps.

Additionally, newer versions of Node.js have included many improvements that we would like to leverage, such as runtime-native common utilities (e.g. `fs.glob` and `util.parseArgs`) and entire new batteries-included modules (e.g. `node:test`, `node:sqlite`).
VerteDinde marked this conversation as resolved.
Show resolved Hide resolved

### Why upgrade now?

In July 2024, Electron’s Ecosystem Working Group decided to upgrade all packages to the earliest Node version where `require()`of synchronous ESM graphs will be supported (see [nodejs/node#51977](https://github.com/nodejs/node/pull/51977) and [nodejs/node#53500](https://github.com/nodejs/node/pull/53500)) at a future point after that version reaches its LTS date.

We’ve decided to set that update time to January/February 2025. After this upgrade occurs, Node 22 will be the minimum supported version in existing ecosystem packages.

### What action do I need to take?

We’ll strive to maintain compatibility as much as possible. However, to ensure the best support, we encourage you to upgrade your apps to Node 22 or higher.

Note that the Node version running in your project is unrelated to the Node version embedded into your current version of Electron.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good start but I'd go even further, e.g. explaining if your app uses Node 21 but doesn't use any ecosystem apps, they don't need to make any changes (I think?)


### What's next

Please feel free to write to us at [[email protected]](mailto:[email protected]) if you have any questions or concerns. You can also find community support in our official [Electron Discord](https://discord.gg/electronjs).
Loading