31309b0e20
* chore: Use devtools-protocol package Rather than maintain our own protocol we can instead use the devtools-protocol package and pin it to the version of Chromium that Puppeteer is shipping with. The only changes are naming changes between the bespoke protocol that Puppeteer created and the devtools-protocol one.
24 lines
719 B
Markdown
24 lines
719 B
Markdown
<!-- Do not edit this file. It is automatically generated by API Documenter. -->
|
|
|
|
[Home](./index.md) > [puppeteer](./puppeteer.md) > [CDPSession](./puppeteer.cdpsession.md) > [send](./puppeteer.cdpsession.send.md)
|
|
|
|
## CDPSession.send() method
|
|
|
|
<b>Signature:</b>
|
|
|
|
```typescript
|
|
send<T extends keyof ProtocolMapping.Commands>(method: T, ...paramArgs: ProtocolMapping.Commands[T]['paramsType']): Promise<ProtocolMapping.Commands[T]['returnType']>;
|
|
```
|
|
|
|
## Parameters
|
|
|
|
| Parameter | Type | Description |
|
|
| --- | --- | --- |
|
|
| method | T | |
|
|
| paramArgs | ProtocolMapping.Commands\[T\]\['paramsType'\] | |
|
|
|
|
<b>Returns:</b>
|
|
|
|
Promise<ProtocolMapping.Commands\[T\]\['returnType'\]>
|
|
|