We’re using @amazon-devices/appium-kepler-driver@3.31.0 for vegaOS device testing and have run into two issues we’d like to raise:
Node 24/25 support
The current engines field only covers up to Node 22:
“node”: “^16.13.0 || ^18.0.0 || ^20.0.0 || ^22.0.0”
Running the driver on Node 24/25 triggers EBADENGINE warnings and compatibility issues. Are there plans to extend support to Node 24/25?
Appium 3.x support
Is there a plan to support Appium 3.x? The current dependency on Appium 2.x creates several issues:
Security vulnerabilities:
Appium 2.x dependencies contain 21 high severity known vulnerabilities including SSRF, prototype pollution, and command injection.
Thank you for raising these questions about @amazon-devices/appium-kepler-driver compatibility.
Regarding Node 24/25 support: The currently supported and documented configuration for Vega Appium integration is Node versions covered by the driver’s engines field (^16.13.0 || ^18.0.0 || ^20.0.0 || ^22.0.0). We recommend using Node 22 (LTS) for the most stable experience with the current driver version.
I’ve shared your request for Node 24/25 support with the team for consideration in a future release.
I understand your concerns about the security vulnerabilities in Appium 2.x dependencies. I’ve escalated this feedback - including the request for Appium 3.x support and the dependency vulnerability concerns - to the team.
In the meantime, for a stable setup we recommend:
Node 22 (LTS)
Appium Server 2.2.2
@amazon-devices/appium-kepler-driver@3.30.0 (the documented version)
I’ll update this thread once I have more information.