You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're having issues in our CI due to peerDependency mismatch:
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/webdriverio
npm error dev webdriverio@"^9.2.11" from the root project
npm error webdriverio@"9.4.0" from @wdio/[email protected]
npm error node_modules/@wdio/cli
npm error dev @wdio/cli@"^9.2.11" from the root project
npm error 3 more (@wdio/globals, expect-webdriverio, @wdio/runner)
npm error
npm error Could not resolve dependency:
npm error peerOptional webdriverio@"^8.32.2" from [email protected]
npm error node_modules/wdio-vscode-service
npm error dev wdio-vscode-service@"^6.1.2" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/webdriverio
npm error peerOptional webdriverio@"^8.32.2" from [email protected]
npm error node_modules/wdio-vscode-service
npm error dev wdio-vscode-service@"^6.1.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/runner/.npm/_logs/2024-11-27T06_43_57_241Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-11-27T06_43_57_241Z-debug-0.log
Error: Process completed with exit code 1.
The current work-around we've found is adding the following to our package.json:
But adding the above may later easily be forgotten and overlooked while also becoming the cause of other issues related to webdriverio version.
It would be ideal that the peerDependencies of wdio-vscode-service are set such that users of this lib can use the latest major webdriverio version without any issues or need for overrides.
The text was updated successfully, but these errors were encountered:
maninak
changed the title
Outdated peerDependency webdriverio@"^8.32.2" causing issues when using latest webdriverio@"^9"
Outdated peerDependency webdriverio@"^8.32.2" causing issues when using latest webdriverio@"^9"Nov 27, 2024
QZera
added a commit
to cytechmobile/radicle-vscode-extension
that referenced
this issue
Dec 31, 2024
- Downgrades WebdriverIO and relevant packages from v9 to v8
There is an incompatibility between WebdriverIO v9 and the "wdio-vscode-service" package. While the
tests execute successfully, there are type-related issues between the two packages. Additionally,
there may be other underlying issues that have not yet been identified.
We can upgrade back to WebdriverIO v9 once the "wdio-vscode-service" package updates its peer
dependencies to support it.
Relevant PR: webdriverio-community/wdio-vscode-service#130
Relevant Issue: webdriverio-community/wdio-vscode-service#140
Signed-off-by: Zacharias Fragkiadakis <[email protected]>
We're having issues in our CI due to peerDependency mismatch:
The current work-around we've found is adding the following to our package.json:
But adding the above may later easily be forgotten and overlooked while also becoming the cause of other issues related to webdriverio version.
It would be ideal that the peerDependencies of
wdio-vscode-service
are set such that users of this lib can use the latest majorwebdriverio
version without any issues or need for overrides.The text was updated successfully, but these errors were encountered: