fix: declare webdriverio as a dependency, not a peer (install parity)#45
Merged
AakashHotchandani merged 1 commit intoJul 13, 2026
Conversation
… peer The extraction moved webdriverio from dependencies (as in the WebdriverIO monorepo / the published @wdio/browserstack-service@9.29.1) into peerDependencies (^9.0.0). That forces the consumer's webdriverio to ^9 and npm ERESOLVEs against any dep peering webdriverio@^7||^8 (e.g. wdio-chromedriver-service@^8) — an install failure the monorepo package never had. Move it back to dependencies to restore install parity. Verified: official npm 9.29.1 and monorepo source both keep webdriverio in dependencies and peer only @wdio/cli; the standalone was the sole divergence. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
AakashHotchandani
requested review from
pri-gadhiya and
vivianludrick
and removed request for
a team
AakashHotchandani
merged commit bf5de42
into
migration/monorepo-add-wdio-browserstack-service
4 checks passed
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.
Problem
Installing the standalone
@wdio/browserstack-servicetgz fails withnpm ERESOLVEin projects that also depend on a package peeringwebdriverio@"^7 || ^8"(e.g.wdio-chromedriver-service@^8) — a failure the monorepo-published package never had.Root cause
The extraction moved
webdriveriofromdependencies→peerDependencies(^9.0.0). That peer forces the consumer'swebdriverioto^9, colliding with the other package's^7||^8peer.Verified this is the only divergence (same version, 9.29.1):
webdriverioworkspace:*9.29.1^9.0.0@wdio/cli@wdio/logger/reporter/typesProof
webdriveriodep/peer placement.Fix
Move
webdriverioback todependencies(matching the upstream package), so the standalone installs identically to what users get today. No user-facing API change — this restores the "zero-change" parity goal of the extraction.Lockfile diff is minimal:
webdriveriowas already resolved (npm auto-installs peers), so it's just reclassified under the service package node.🤖 Generated with Claude Code