Repository navigation
chore(deps): move the workspace to WebdriverIO 10 - #434
Merged
Merged
Conversation
Contributor
 [High impact] The PR appears safe to merge; no new actionable issues were found. SummaryMoves the workspace to WebdriverIO 10 and raises the published backend, service, and adapter requirements to Node 22.19+.
Reviews (5) · Last reviewed commit: "feat!: require Node 22.19 across the pub..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
vishnuv688
force-pushed
the
feat/300-wdio-scenario
branch
from
October 19, 2026 11:43
4e93f4f to
f3eb951
Compare
vishnuv688
force-pushed
the
chore/wdio-10
branch
from
October 19, 2026 11:43
a36c450 to
d5319e7
Compare
@wdio/protocols 10 removes the Mobile JSON Wire Protocol table, which no current driver speaks. The Log tab spread it into the command definitions it describes a selected command with; every other table is still read, so a command's description is unchanged for anything a session can issue today.
Every WebdriverIO dependency moves to its 10.x line: the root CLI and webdriverio, the examples, the app's browser runner and framework, the conformance scenario, elements, the backend's logger and the adapters' logger and webdriverio. Peers that pnpm used to auto-install at the locked 9.x versions (webdriverio for the service and elements, @wdio/cli for the backend, @wdio/allure-reporter for the service) are declared, so no package resolves a 9.x copy; expect-webdriverio moves to 8.0.0 beside the globals that require it. Published peer ranges stay at ^9 || ^10 and the wdio-peer job keeps covering both. The new types parent an element with a held browsing context, which carries its browser, so the service's walk up to the browser resolves that case as @wdio/utils does.
@wdio/logger 10 and webdriverio 10 require Node 22.19, where the 9.x lines run on Node 18.20. The backend is what the Python adapter launches on a Node its README promises can be 18, and the service installs that backend for a project that may still run WebdriverIO 9 on Node 20, so moving those runtime dependencies would have raised every consumer's Node floor without saying so. The 10.x toolchain stays for building and testing; the runtime dependency lines go back, and the changesets that announced them with it.
The backend's and the protocol adapters' runtime dependencies move to the WebdriverIO 10 lines, which declare Node 22.19 in their engines, so the packages declare that floor themselves instead of implying 18.20 through the 9.x lines. Node 18 and 20 are past end of life and CI never ran on them; a WebdriverIO 9 project on Node 22 is unaffected, and the service's peer range stays ^9 || ^10. The Python adapter checks the minor as well as the major up front, since a Node 22.0 would otherwise fail later as a backend spawn timeout, and both READMEs state the new floor.
vishnuv688
force-pushed
the
feat/300-wdio-scenario
branch
from
October 19, 2026 12:08
f3eb951 to
1693dcc
Compare
vishnuv688
force-pushed
the
chore/wdio-10
branch
from
October 19, 2026 12:08
d5319e7 to
929f99b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #433 (WDIO conformance scenario); base is
feat/300-wdio-scenario.What
The toolchain the workspace builds and tests with moves to the 10.x line: the root CLI and
webdriverio,examples/wdio,packages/app(browser runner, mocha framework, protocols, reporter, globals),packages/conformance,packages/elements, and the service's and backend's development dependencies. Peers that were auto-installed before (webdriveriofor the service and elements,@wdio/clifor the backend,@wdio/allure-reporterfor the service) are declared, so no development dependency resolves a 9.x copy.expect-webdriveriomoves to 8.0.0 beside the globals that require it.The published packages' runtime dependencies stay on their 9.x lines (
@wdio/loggerin the backend and both protocol adapters,webdriverioin the adapters):@wdio/logger10 andwebdriverio10 require Node 22.19, while the 9.x lines run on Node 18.20, which the Python adapter's README promises for the backend it launches and which a service user on WebdriverIO 9 still has. Published peer ranges are unchanged (^9 || ^10), and thewdio-peerjob keeps running the service under both majors.Source changes the new types required
packages/app/src/components/workbench/logs.ts:@wdio/protocols10 removed the MJSONWP table, so the Log tab's command definitions no longer spread it.packages/service/src/utils.tsgetBrowserObject: WebdriverIO 10 can parent an element with a held browsing context, which carries its browser, so the walk up the parent chain now resolves that case as@wdio/utilsdoes. Regression test added.Changesets: service (the context walk-up), app (the dropped table). No runtime dependency line changes, so the backend and the protocol adapters carry none.
Verification
pnpm build,pnpm lint,pnpm testare green, including the conformance suite for all four adapters in both modes; the WDIO scenario now runs under WebdriverIO 10.pnpm install --frozen-lockfilereproduces the lockfile.pnpm test:ui(browser runner 10 under the workspace's vite 8 override) andpnpm demo:wdio,pnpm demo:wdio:mocha.Registry note
pnpm's registry metadata for
expect-webdriveriostill lacked 8.0.0 on this machine while the registry's document had it (published 2026-10-10), so the lockfile was resolved from the registry's current document. The frozen install, which only needs the package tarballs, verifies the result.