Skip to content
This repository was archived by the owner on Feb 22, 2026. It is now read-only.

Add support for Node.js 24 and drop unused fields#1140

Open
LitoMore wants to merge 3 commits into
i18next:masterfrom
LitoMore:update-engines
Open

Add support for Node.js 24 and drop unused fields#1140
LitoMore wants to merge 3 commits into
i18next:masterfrom
LitoMore:update-engines

Conversation

@LitoMore

Copy link
Copy Markdown

Why am I submitting this PR

Node.js 24 is out, so we can consider adding Node.js 24 to the engines field.

The npm and yarn fields in engines can be removed since those versions are too old. We can drop them gracefully.

I also updated the GitHub Actions workflow file to test with Node.js 24.

Does it fix an existing ticket?

No

Checklist

  • only relevant code is changed (make a diff before you submit the PR)
  • do no modify the version in package.json or CHANGELOG.md
  • tests are included and pass: yarn test (see details here)
  • documentation is changed or added

Comment thread package.json Outdated
@saitheexplorer

Copy link
Copy Markdown

Any updates on this? Trying to install another package that has this as a dependency and yarn is blocking the install because we're running node v24

@DannyvanHolten

Copy link
Copy Markdown

Can we please merge this :)

@sharknoon

Copy link
Copy Markdown

I am also running into the same Unsupported engine warning. All my other dependencies already support node.js 24 (which will become LTS in october 2025), ecxept the i18next-parser.

grafik

@adrai

adrai commented Oct 1, 2025

Copy link
Copy Markdown
Member

fyi: #1148

Comment thread package.json
"node": "^18.0.0 || ^20.0.0 || ^22.0.0",
"npm": ">=6",
"yarn": ">=1"
"node": ">=18"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This is great since Node is very unlikely to break support for the APIs needed by this library, and this way it doesn't need continuous updating from the repo owner 🙏

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants