Skip to content

🧹 Versioning: Bump minimum Node.js version from 18.18.0 to 20.19.0 #5358

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.

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

Open
JoshuaKGoldberg opened this issue May 6, 2025 · 0 comments
Labels
core-team issues which must be handled by Mocha's core team semver-major implementation requires increase of "major" version number; "breaking changes"
Milestone

Comments

@JoshuaKGoldberg
Copy link
Member

Overview

We're gearing up for a new major version of Mocha, Mocha 12 (#5357). That means we can bump the minimum Node engine version! Hooray! This is great for a couple of reasons:

Node.js 18 went EOL April 30 2025. Node.js 20 is still LTS for another year, through April 30 2026. Node.js ^20.19.0 || >=22.12.0 is the minimum version that supports unflagged require(ESM).

So, our current thought for Mocha 12 is to raise the minimum Node.js version to ^20.19.0 || >=22.12.0.

Note: see #5226 -> #5354 for our policy on supported browser versions (still in review at time of posting). Node.js 20.0.0 was released on April 18, 2023, so the equivalent browser versions would be:

@JoshuaKGoldberg JoshuaKGoldberg added core-team issues which must be handled by Mocha's core team semver-major implementation requires increase of "major" version number; "breaking changes" labels May 6, 2025
@JoshuaKGoldberg JoshuaKGoldberg added this to the v12.0.0 milestone May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-team issues which must be handled by Mocha's core team semver-major implementation requires increase of "major" version number; "breaking changes"
Projects
None yet
Development

No branches or pull requests

1 participant