feat(cdp): implementation of cdp-bridge

[mato533]

This new package (@wdio/cdp-bridge) will be used to connect the node debugger.

*) This PR uses the IPC-Bridge replacement development branch ‘ta/cdp/main’ as the Base Branch.

[mato533]

@goosewobbler
If you think it is better to review the contents of this new package after looking at the entire code replace IPC -Bridge, please comment on this.
This PR will be merged immediately.

We will create another pull request with base as main to close #308, based on the base branch of this PR.

[goosewobbler]

Let's get #952 done, and the other v8 PRs (#996, #960, #978, #956) merged, do a second v8.x release. Then we can look at the v9 stuff.

[mato533]

@goosewobbler
I agree that this should be considered after the PRs you mentioned has been completed.

After that, I would like to discuss the possibility of releasing this change as part of v8 (minor update).
At the moment, this PR is created in such a way that it does NOT cause a BREAKING CHANGES from the user's point of view.

[goosewobbler]

I see - well, it doesn't NEED to be released before v9 as nothing in v8.x.y will use the new package.

However I'm not against getting the new package published as part of 8.x.y if it will make the v9 dev easier in some way...

[mato533]

@goosewobbler
I'll update to get rid of the asset that's needed for backward compatibility toward v8.
For example, remove preload/main script, remove dependencies of sample apps to this service, etc...

It will also be possible to test when ‘feature/v9’ is created and v9.next can be released.

Update

We have completed to get rid of the code related for backward compatibility.(the commit belongs to #969)

[goosewobbler]

@mato533 I created feature/v9 from ta/cdp/main

[mato533]

@mato533 I created feature/v9 from ta/cdp/main

@goosewobbler
Thank you for your operation.
But It seems that the name feature/v9 is conflicted between the changes of #1025 .

[Copilot]

Pull Request Overview

This PR implements a new package (@wdio/cdp-bridge) that provides a lightweight interface for connecting to the Node debugger via the Chrome Developer Protocol (CDP). Key changes include:

• Adding package configuration to the monorepo (pnpm-workspace.yaml)
• Implementing the main library files for connecting to the debugger (dev-tool, bridge, types, constants)
• Adding unit and end-to-end tests as well as build configuration via Rollup and documentation in the README

Reviewed Changes

Copilot reviewed 12 out of 18 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
pnpm-workspace.yaml	Added new package entry for cdp-bridge
packages/@wdio_electron-cdp-bridge/vitest.config.ts	Setup of vitest configuration for the new package
packages/@wdio_electron-cdp-bridge/test/dev-tool.spec.ts	Unit tests for DevTool functionality
packages/@wdio_electron-cdp-bridge/test/bridge.spec.ts	Unit tests for CdpBridge covering connection, messaging, etc.
packages/@wdio_electron-cdp-bridge/src/types.ts	Type definitions for debugger info and version data
packages/@wdio_electron-cdp-bridge/src/index.ts	Entry point re-exporting public API components
packages/@wdio_electron-cdp-bridge/src/dev-tool.ts	Implements debugger connection and request execution
packages/@wdio_electron-cdp-bridge/src/constants.ts	Declaration of default settings and error messages
packages/@wdio_electron-cdp-bridge/src/bridge.ts	Implements the bridge class for sending commands and handling events
packages/@wdio_electron-cdp-bridge/rollup.config.ts	Build configuration for both ESM and CJS modules
packages/@wdio_electron-cdp-bridge/e2e/node.spec.ts	End-to-end tests for cdp-bridge functionality
packages/@wdio_electron-cdp-bridge/README.md	Documentation and usage examples for the new package

Files not reviewed (6)

• packages/@wdio_electron-cdp-bridge/e2e/tsconfig.json: Language not supported
• packages/@wdio_electron-cdp-bridge/package.json: Language not supported
• packages/@wdio_electron-cdp-bridge/test/tsconfig.json: Language not supported
• packages/@wdio_electron-cdp-bridge/tsconfig.json: Language not supported
• pnpm-lock.yaml: Language not supported
• turbo.json: Language not supported

Comments suppressed due to low confidence (1)

packages/@wdio_electron-cdp-bridge/README.md:3

• [nitpick] Replace the non-standard hyphen 'ー' with a standard hyphen '-' in the package name URL.

<a href="https://www.npmjs.com/package/@wdio/cdpーbridge" alt="NPM Version">

[goosewobbler]

@mato533 I created feature/v9 from ta/cdp/main

@goosewobbler Thank you for your operation. But It seems that the name feature/v9 is conflicted between the changes of #1025 .

Not sure what you mean here, you mean it has merge conflicts with main now? We can just recreate it before merge...

EDIT: just recreated feature/v9 from main and rebased

[mato533]

@mato533 I created feature/v9 from ta/cdp/main

@goosewobbler Thank you for your operation. But It seems that the name feature/v9 is conflicted between the changes of #1025 .

Not sure what you mean here, you mean it has merge conflicts with main now? We can just recreate it before merge...

EDIT: just recreated feature/v9 from main and rebased

Sorry....it's so hard to understand....
Based on following logic, the feature branch name for the v9 should be feature/v9.x nor feature/v9.
This is what I wanted to say....

wdio-electron-service/.github/workflows/_release-calculate.reusable.yml

Lines 89 to 92 in 519f967

	if [ "${BRANCH_TYPE}" == 'feature' ]; then
	# For feature branches, use as-is
	echo "target_branch=feature/v${FEATURE_MAJOR_VERSION}.x"
	echo "target_branch=feature/v${FEATURE_MAJOR_VERSION}.x" >> $GITHUB_OUTPUT

[goosewobbler]

Got it, haha! We started off using v9 and then changed it.