The Node.js support story needs a decision:
package.json engines say >=18, and the CI matrix tests 18/20/22.- Node 18 reached end-of-life in April 2025 — advertising support for an EOL runtime in a security-focused library sends the wrong signal.
- There is no
.nvmrc, so contributors don't get a pinned local version.
To decide
- Raise the floor to
>=20 (drop 18 from engines and the CI matrix, add 24 to the matrix)? Note this is technically breaking for anyone still on 18, so it should ride the next appropriate release.
- Add
.nvmrc with the primary development version (the one used for the lint/publish CI jobs).
Filing as a question first — once the floor is decided, the implementation is a good first issue.
The Node.js support story needs a decision:
package.jsonengines say>=18, and the CI matrix tests 18/20/22..nvmrc, so contributors don't get a pinned local version.To decide
>=20(drop 18 from engines and the CI matrix, add 24 to the matrix)? Note this is technically breaking for anyone still on 18, so it should ride the next appropriate release..nvmrcwith the primary development version (the one used for the lint/publish CI jobs).Filing as a question first — once the floor is decided, the implementation is a good first issue.