webdriverio: [🐛 Bug]: @wdio/cli broken since 8.16.12

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Version

8.16.12

Node.js Version

20.7.0

Mode

WDIO Testrunner

Which capabilities are you using?

{
  runner: 'local',
  user: ConfigSettings.browserStackUser,
  key: ConfigSettings.browserStackKey,
  browserStackLocal: true,
}

What happened?

Connecting to Browserstack works fine with @wdio/cli version 8.16.11 but starting from 8.16.12 we get the error als shown below.

We execute WDIO from inside an Alpine Docker image.

What is your expected behavior?

With version @wdio/cli@8.16.11 the connection with Browserstack still worked. We updated all other WDIO dependencies to 8.16.15 and that still worked.

How to reproduce the bug.

There is no reproducable code. If needed I can try to create a small project that has this issue.

Dependencies:

  "dependencies": {
    "@wdio/cli": "8.16.12",
    "@wdio/jasmine-framework": "8.16.15",
    "@wdio/junit-reporter": "8.16.12",
    "@wdio/local-runner": "8.16.15",
    "@wdio/spec-reporter": "8.16.12",
    "browserstack-local": "1.5.4",
    "ts-node": "10.9.1",
    "typescript": "5.2.2"
  }

Relevant log output

Error while trying to execute binary Error: Command failed: /root/.browserstack/BrowserStackLocal --daemon start --log-file /web-vr-lib/vr/local.log --source nodejs-1.5.4 --key <REDACTED> --local-identifier <REDACTED> --force --verbose 1
Pkg: FLAGS_MISMATCH

    at ChildProcess.exithandler (node:child_process:422:12)
    at ChildProcess.emit (node:events:514:28)
    at ChildProcess.emit (node:domain:488:12)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 4,
  killed: false,
  signal: null,
  cmd: '/root/.browserstack/BrowserStackLocal --daemon start --log-file /web-vr-lib/vr/local.log --source nodejs-1.5.4 --key <REDACTED> --local-identifier <REDACTED> --force --verbose 1'
}

Code of Conduct

• I agree to follow this project’s Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues