Repository navigation
chore: support Node versions beyond 24 across the ecosystem #339
Description
Part of #334.
Problem
Every package declares "engines": { "node": ">=24 <25" } and the docs say Node 24 is required. A developer on Node 22 (still LTS) or a newer release gets engine warnings or failures before seeing anything work.
Proposal
- Decide the supported range (suggest
>=22) and test it in CI with a version matrix - Update
enginesin: seamless-auth-api, seamless-auth-server (all packages), seamless-auth-react (all packages), seamless-auth-types, seamless-cli, seamless-templates, seamless-auth-admin-dashboard - Update docs prerequisites
Activity
chore: support Node 22 and newer (#165)
chore: support Node 22 and newer (#188)
chore: support Node 22 and newer (#353)
chore: support Node 22 and newer (#88)
Bccorb commentedon Oct 7, 2026
Done. Every package now declares
engines.node >=22and CI runs on Node 22, 24 and the latest release. Merged: #353, fells-code/seamless-auth-types#88, fells-code/seamless-auth-server#188, fells-code/seamless-auth-react#165, fells-code/seamless-cli#226, fells-code/seamless-templates#102, fells-code/seamless-auth-admin-dashboard#281, fells-code/seamless-auth-messaging#8, fells-code/seamless-auth-docs#56. Published packages pick up the new range on their next release.