[2.x] Update CI node version to 24

[limzykenneth]

Changes:
All CI now runs Node.js 24 where needed, this should have LTS for quite awhile yet

[p5-bot]

Continuous Release

CDN link

• https://raw.esm.sh/pr/p5@16219e5/lib/p5.min.js

Published Packages

• https://pkg.pr.new/p5@16219e5

Commit hash: 4b2c166

Previous deployments

a7d9d37

• https://raw.esm.sh/pr/p5@006e1c7/lib/p5.min.js
• https://pkg.pr.new/p5@006e1c7

---

This is an automated message.

[Vaivaswat2244]

Hey @limzykenneth! Here, Chrome is present on the runner but WebDriverIO fails to establish a ChromeDriver session within the timeout. No ChromeDriver process ever starts, which is why Vitest times out waiting for the browser session.
From local testing, the root cause appears to be that WebDriverIO's automatic ChromeDriver download/unpack step is creating the destination folder but failing to place the binary inside it, so ChromeDriver never launches. The download URL itself is reachable and the zip is valid. manually unpacking it to the expected path (/tmp/chromedriver/linux-/chromedriver-linux64/chromedriver) and then running the tests works fine, which confirms the test infrastructure itself (Vitest + WebDriverIO + Chrome) is sound.
I wasn't able to fully reproduce and fix this locally since the unpack failure appears to be environment-specific. However the CI runner shows the same symptom — ChromeDriver session timeout — so the underlying cause is likely the same.
A possible fix worth trying is adding an explicit ChromeDriver install step to the CI workflow before running tests, to bypass WebDriverIO's automatic download entirely:

- name: Install ChromeDriver
  run: npx wdio install chromedriver

This would ensure ChromeDriver is present and executable before Vitest tries to connect to it, regardless of whether WebDriverIO's auto-download works in that environment.
Happy to help test further if you can point me to a way to reproduce the CI environment more closely.

Additionally,
This didn't fail on Node 20 because the GitHub Actions runner image tied to Node 20 shipped with an older Chrome version that WebDriverIO 9.0.7 was compatible with. Bumping to Node 24 pulled in a newer runner image with Chrome 148, which WebDriverIO 9.0.7 can't reliably download a matching ChromeDriver for or connect to.

[limzykenneth]

Thanks @Vaivaswat2244! I can replicate this locally and it seems to be something flaky, I'll look into it here and might switch to playwright instead

[limzykenneth]

Nevermind this for now. I plan to do a more complete dependencies updates for 2.x soon and it's more streamlined to do it all then.

[Vaivaswat2244]

Sure! Please lmk if you need any help around this. Thanks!