Node.js libraries for interfacing with the Chrome DevTools Protocol
Перейти к файлу
dependabot[bot] 252a985eb7
Bump tough-cookie from 4.0.0 to 4.1.3 (#11)
Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) from 4.0.0 to 4.1.3.
- [Release notes](https://github.com/salesforce/tough-cookie/releases)
- [Changelog](https://github.com/salesforce/tough-cookie/blob/master/CHANGELOG.md)
- [Commits](https://github.com/salesforce/tough-cookie/compare/v4.0.0...v4.1.3)

---
updated-dependencies:
- dependency-name: tough-cookie
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-09-04 16:57:43 -07:00
.vscode add server and some unit tests for the connection 2021-06-11 18:29:54 -07:00
src flesh out server and client 2021-07-08 16:42:18 -07:00
.eslintrc.js init 2021-06-08 18:38:48 -07:00
.gitignore init 2021-06-08 18:38:48 -07:00
.npmignore init 2021-06-08 18:38:48 -07:00
CHANGELOG.md flesh out server and client 2021-07-08 16:42:18 -07:00
CODE_OF_CONDUCT.md CODE_OF_CONDUCT.md committed 2021-06-08 16:30:57 -07:00
LICENSE LICENSE committed 2021-06-08 16:30:57 -07:00
README.md flesh out server and client 2021-07-08 16:42:18 -07:00
SECURITY.md SECURITY.md committed 2021-06-08 16:30:59 -07:00
SUPPORT.md SUPPORT.md committed 2021-06-08 16:30:59 -07:00
ci.yml Update ci.yml 2023-03-15 09:42:33 -07:00
jest.config.js flesh out server and client 2021-07-08 16:42:18 -07:00
package.json chore: onboard to npm pipeline 2022-12-13 11:59:52 -08:00
tsconfig.json flesh out server and client 2021-07-08 16:42:18 -07:00
yarn.lock Bump tough-cookie from 4.0.0 to 4.1.3 (#11) 2024-09-04 16:57:43 -07:00

README.md

vscode-cdp

This package exports strongly-typed client and server implementations for the Chrome DevTools Protocol. These implementations are extensible with additional domains, and some handling of sessions and sockets is also included out of the box.

Quickstart

Most likely, you're using this as a consumer of a CDP server (e.g. a browser or js-debug).

import { Connection, WebSocketTransport } from '@vscode/cdp';

// Acquire your connection to a browser, somehow, and then create a typed CDP wrapper.
const myWebSocket = await connectToBrowser();
const cdpClient = Connection.client(new WebSocketTransport(myWebSocket));

// You can then call methods in a strongly-typed way...
await cdpClient.rootSession.api.Debugger.enable();

// and also listen to them!
cdpClient.rootSession.api.Debugger.onPaused(evt => {
	console.log(evt.callFrames);
});

Advanced Scenarios

Custom Domains

By default, the Connection.client will by typed with the domains exposed by V8 and Chrome. However, this package also exports the undocumented Node.js-specific domains, and you can mix in custom domains. For example:

import { Connection, WebSocketTransport, CdpV8, CdpBrowser, CdpNode } from '@vscode/cdp';
// Uses "MyCustomDomains" from the Server Implementation section below:
type AllMyDomains = CdpV8.Domains & CdpBrowser.Domains & CdpNode.Domains & MyCustomDomains;
const cdpClient = Connection.client<AllMyDomains>(new WebSocketTransport(myWebSocket));

Server Implementation

You can also implement a CDP server. Once again, this is all strongly-typed. You'll want to pass in a generic to Connection.server which is a map of domain names to IDomain interfaces, which define methods and events:

interface MyCustomDomains {
	Greeter: {
		events: {
			didGreet: { params: string };
		};
		requests: {
			hello: {
				params: { name: string; emit?: boolean; throw?: boolean };
				result: { greeting: string };
			};
		};
	};
}

webSocketServer.on('connection', ws => {
	const cdpServer = Connection.server<MyCustomDomains>(new WebSocketTransport(ws));

	cdpServer.rootSession.api = {
		Greeter: {
			async hello(client, args) {
				client.Greeter.didGreet(args.name);
				return { greeting: `Hello ${args.name}!` };
			},
		},
	};
});

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.