Closed (won't fix)
Project:
Drupal core
Version:
10.5.x-dev
Component:
javascript
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Dec 2024 at 17:04 UTC
Updated:
13 Jan 2026 at 21:23 UTC
Jump to comment: Most recent
Comments
Comment #3
spokjeI tried this but also got shipwrecked on the Selenium session bit, probably some new config option we have to pass somewhere?
Oh, and all the resolutions we all love to hate in the package.json are there because of Nightwatch holding at 2.4.2.
If we get it higher, we can drop all of them AFAICT.
Comment #4
spokjeAnd as a side-note: This MR also seems to bump cspell from version "8.16.1" to version "8.17.1".
Perhaps by deleting the yarn.lock before doing a yarn install?
Comment #5
cpierce42I've been experimenting with this in lando (wsl2, drupal 10.4) tying to upgrade nightwatchjs to version 3.11.0.
This ticket https://www.drupal.org/project/drupal/issues/3371963#comment-15134159 said it would be ported into D10.3+ but it did not get rolled in.
I am attempting to re-work the merge reqeust that was submitted and making it work but there is something missing.
I got it pretty close where it starts a selenium server but hangs:
Nothing else happens and the log file is blank.
Specifically to get to this point I preformed the following steps:
write a patch to allow changes from the above mentioned ticket to apply in composer
Install linux current chromium driver on both wsl and in the lando build_as_root
apt install libnss3-dev libgdk-pixbuf2.0-dev libgtk-3-dev libxss-devIn my lando file I have a lot of changes:
In the nightwatch.config.js file I changed the selenium start_process to true, added plugins:['@nightwatch/vrt']
Comment #7
longwaveAt this stage in Drupal 10's life to me this is won't fix, I don't think it's worth spending any more effort on.
Comment #9
quietone commentedYea, I was just checking if anything changed so that tests would pass. I neglected to come back and close this.
longwave and I agree that this is now a won't fix.