[Question] Should `engines.node` be bumped to 20+?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 316
- Forks
- 98
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 2
Description
👋 Hello!
I noticed the README currently states:
Currently, Node 18+ is supported. We support the LTS versions of Node. You can add the node package to your CLI to ensure users are running a specific version of Node.
However, node18 is no longer LTS (ended 27 Mar 2025) https://endoflife.date/nodejs
Q) Would you accept a PR to update the relevant configs/CI/docs to upgrade to node 20 (EOL - 30 Apr 2026), or maybe even node22?
Node 20 (EOL - 30 Apr 2026) brings a backported require(esm) support 🥳
Node 22 (EOL - 30 Apr 2027) introduces --experimental-strip-types (the default in 23/24), which could have some performance opportunities 👀
Let me know what you think!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Node.js support statement in README and inspect the relevant package configuration, CI, and documentation files mentioned in the issue. Determine whether the project should target Node 20 or 22, then verify that the updated runtime requirement and CI support are consistent before considering the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- ci-cd, cli, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100