cypress-io
WebKit browser version reported as 0 when linking to a globally installed playwright-webkit package
Current behavior
If you use npm link playwright-webkit to link to a version of playwright-webkit previously installed globally via npm install -g playwright-webkit then the version reported by Cypress is shown as 0
(Run Starting)
┌─────────────────────────────────────────────────────────────────────────────┐ │ Cypress: 12.3.0 │ │ Browser: WebKit 0 (headless) │ │ Node Version: v16.16.0 (/usr/local/bin/node) │
Relevant debug output reports:
cypress:server:browsers:utils searching for browser { nameOrPath: 'webkit', filter: { name: 'webkit', channel: 'stable' }, knownBrowsers: [ { name: 'webkit', channel: 'stable', family: 'webkit', displayName: 'WebKit', version: '0', path: '/root/.cache/ms-playwright/webkit-1751/pw_run.sh', majorVersion: '0', warning: 'WebKit support is currently experimental. Some functions may not work as expected.' } ] } +2s
This is in contrast to what is reported when the npm install --save-dev playwright-webkit command is used:
(Run Starting) ┌─────────────────────────────────────────────────────────────────────────────┐ │ Cypress: 12.3.0 │ │ Browser: WebKit 16 (headless) │ │ Node Version: v16.16.0 (/usr/local/bin/node) │
Relevant debug output reports:
cypress:server:browsers:utils searching for browser { nameOrPath: 'webkit', filter: { name: 'webkit', channel: 'stable' }, knownBrowsers: [ { name: 'webkit', channel: 'stable', family: 'webkit', displayName: 'WebKit', version: '16.4', path: '/root/.cache/ms-playwright/webkit-1751/pw_run.sh', majorVersion: '16', warning: 'WebKit support is currently experimental. Some functions may not work as expected.' } ] } +2s
Desired behavior
The version reported by using the npm link command should reflect that outputted by the npm install command.
Test code to reproduce
Not entirely sure this would help in this case as it's related to environment setup.
Cypress Version
12.3.0
Node version
16.16.0
Operating System
5.10.102.1-microsoft-standard-WSL2
Debug Logs
See above
Other
No
Hi @martinsik , Unfortunately at this time we do not fully support WSL or WSL2. Are you seeing the same behavior on native linux?
I'm seeing this behaviour inside our docker cotainers, which run on WSL2 during development but then on a native linux box for our overnight tests. That box is reporting as 5.15.0-53-generic.
