Chore: Support newer Node versions (24 LTS / 25) for agor-live #278
Description
Feature request
Would you be open to:
- Bumping the
engines.noderange to include Node 24 LTS / Node 25 (after testing), and - Updating any dependencies that currently block newer Node versions?
Environment
- Node v25.2.0
- npm 11.6.2
- OS: Arch Linux
npm install -g agor-live@latest works but shows EBADENGINE warnings:
[email protected]requiresnode >=20.0.0 <21.0.0@homebridge/[email protected]requiresnode >=18.0.0 <25.0.0
Actual console output:
npm install -g agor-live@latest
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '[email protected]',
npm warn EBADENGINE required: { node: '>=20.0.0 <21.0.0' },
npm warn EBADENGINE current: { node: 'v25.2.0', npm: '11.6.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@homebridge/[email protected]',
npm warn EBADENGINE required: { node: '>=18.0.0 <25.0.0' },
npm warn EBADENGINE current: { node: 'v25.2.0', npm: '11.6.2' }
npm warn EBADENGINE }
npm warn deprecated [email protected]: Use your platform's native DOMException instead
added 3 packages, removed 2 packages, and changed 669 packages in 35s
137 packages are looking for funding
run `npm fund` for detailsBehavior on Node 25
[email protected]has issues on Node 25.2.0 in my setup. purely because it doesn't support the latest node versions in packages.
Background
I have a script that updates everything on my machine, and I kept wondering why npm was never showing any updates for agor-live while other global packages moved forward. I’d been using the dev version because I assumed the live CLI was stuck or broken.
When I tried to update manually, I noticed the EBADENGINE warnings above. That explains the behavior, and I’ve now updated my update script to fail on warnings instead of exiting with 0.
Thanks for all the work on Agor, it’s been really helpful in my workflow (the dev version I've been using has lol)!