@Danp said:
Node v24 should work fine. The reason for your failure is here --
error eslint-visitor-keys@5.0.1: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.13.0 || >=24". Got "23.11.0"
Either upgrade Node to v24 or downgrade it to v22.
So this is not correct? I do remember running into other issues when on node 24. I dont know which specific version of 24 but those problems did go away when i dropped to v22.
Note i am not a program at all just my little knowledge and Claude code...
from Claude code -
Yarn v1 is not officially compatible with Node.js 24.
Yarn v1 Classic is untested on Node.js >= 20 and in maintenance-only mode since 2020
It may still work for basic operations, but it's not supported
There's an active proposal to drop Yarn v1 with Node.js 26 (April 2026)
For XO specifically: Xen Orchestra's build process uses Yarn v1. Running it on Node 24 is likely to cause issues. Stick with Node 22 (the script's default) which is tested and supported.
Sources:
https://github.com/cypress-io/cypress-docker-images/issues/1438
https://endoflife.date/yarn
From Google -
Yes, Node.js 24 is compatible with Yarn v1 (Classic), though you may encounter non-blocking warnings.
GitHub
GitHub
+1
While Yarn v1 remains functional, it is officially in maintenance mode and no longer receives active bug fixes or feature updates.
GitHub
GitHub
+1
Key Compatibility Details
Deprecation Warnings: Running Yarn v1 on Node.js 24 (and newer versions) often triggers a [DEP0169] DeprecationWarning related to url.parse(), as Yarn v1 uses an outdated API that Node.js is phasing out. This warning does not typically stop your build or installation from completing.
Installation with Corepack: Node.js 24 continues to support Corepack, a tool that manages package managers like Yarn. You can enable it by running corepack enable to use the Yarn version specified in your project's package.json.
Planned Removal: There are ongoing discussions about removing Yarn v1 from official Node.js Docker images starting with Node.js 26 in 2026.
Engine Incompatibility: Even if the package manager itself works, individual project dependencies (like Vite) may require specific Node.js versions. If a package expects a different version than Node 24, Yarn v1 will throw an "incompatible module" error.
GitHub
GitHub
+6
If you are starting a new project, it is highly recommended to migrate to Yarn Modern (v4+) or pnpm for better long-term support and performance.
MikeMcC399 created this issue in cypress-io/cypress-docker-images
open
Proposal: remove Yarn v1 Classic with Node.js 26
#1438
