931d4fced5
🤖 I have created a release *beep* *boop* --- <details><summary>puppeteer: 19.4.0</summary> ## [19.4.0](https://github.com/puppeteer/puppeteer/compare/puppeteer-v19.3.0...puppeteer-v19.4.0) (2022-12-07) ### Features * **chromium:** roll to Chromium 109.0.5412.0 (r1069273) ([#9364](https://github.com/puppeteer/puppeteer/issues/9364)) ([1875da6
](1875da6191
)), closes [#9233](https://github.com/puppeteer/puppeteer/issues/9233) ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 19.3.0 to 19.4.0 </details> <details><summary>puppeteer-core: 19.4.0</summary> ## [19.4.0](https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v19.3.0...puppeteer-core-v19.4.0) (2022-12-07) ### Features * ability to send headers via ws connection to browser in node.js environment ([#9314](https://github.com/puppeteer/puppeteer/issues/9314)) ([937fffa
](937fffaedc
)), closes [#7218](https://github.com/puppeteer/puppeteer/issues/7218) * **chromium:** roll to Chromium 109.0.5412.0 (r1069273) ([#9364](https://github.com/puppeteer/puppeteer/issues/9364)) ([1875da6
](1875da6191
)), closes [#9233](https://github.com/puppeteer/puppeteer/issues/9233) * **puppeteer-core:** keydown supports commands ([#9357](https://github.com/puppeteer/puppeteer/issues/9357)) ([b7ebc5d
](b7ebc5d9bb
)) ### Bug Fixes * **puppeteer-core:** avoid type instantiation errors ([#9370](https://github.com/puppeteer/puppeteer/issues/9370)) ([17f31a9
](17f31a9ee4
)), closes [#9369](https://github.com/puppeteer/puppeteer/issues/9369) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
81 lines
3.1 KiB
Markdown
81 lines
3.1 KiB
Markdown
---
|
|
sidebar_label: Page.$$eval
|
|
---
|
|
|
|
# Page.$$eval() method
|
|
|
|
This method runs `Array.from(document.querySelectorAll(selector))` within the page and passes the result as the first argument to the `pageFunction`.
|
|
|
|
#### Signature:
|
|
|
|
```typescript
|
|
class Page {
|
|
$$eval<
|
|
Selector extends string,
|
|
Params extends unknown[],
|
|
Func extends EvaluateFunc<
|
|
[Array<NodeFor<Selector>>, ...Params]
|
|
> = EvaluateFunc<[Array<NodeFor<Selector>>, ...Params]>
|
|
>(
|
|
selector: Selector,
|
|
pageFunction: Func | string,
|
|
...args: Params
|
|
): Promise<Awaited<ReturnType<Func>>>;
|
|
}
|
|
```
|
|
|
|
## Parameters
|
|
|
|
| Parameter | Type | Description |
|
|
| ------------ | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
| selector | Selector | the [selector](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors) to query for |
|
|
| pageFunction | Func \| string | the function to be evaluated in the page context. Will be passed the result of <code>Array.from(document.querySelectorAll(selector))</code> as its first argument. |
|
|
| args | Params | any additional arguments to pass through to <code>pageFunction</code>. |
|
|
|
|
**Returns:**
|
|
|
|
Promise<Awaited<ReturnType<Func>>>
|
|
|
|
The result of calling `pageFunction`. If it returns an element it is wrapped in an [ElementHandle](./puppeteer.elementhandle.md), else the raw value itself is returned.
|
|
|
|
## Remarks
|
|
|
|
If `pageFunction` returns a promise `$$eval` will wait for the promise to resolve and then return its value.
|
|
|
|
## Example 1
|
|
|
|
```ts
|
|
// get the amount of divs on the page
|
|
const divCount = await page.$$eval('div', divs => divs.length);
|
|
|
|
// get the text content of all the `.options` elements:
|
|
const options = await page.$$eval('div > span.options', options => {
|
|
return options.map(option => option.textContent);
|
|
});
|
|
```
|
|
|
|
If you are using TypeScript, you may have to provide an explicit type to the first argument of the `pageFunction`. By default it is typed as `Element[]`, but you may need to provide a more specific sub-type:
|
|
|
|
## Example 2
|
|
|
|
```ts
|
|
// if you don't provide HTMLInputElement here, TS will error
|
|
// as `value` is not on `Element`
|
|
await page.$$eval('input', (elements: HTMLInputElement[]) => {
|
|
return elements.map(e => e.value);
|
|
});
|
|
```
|
|
|
|
The compiler should be able to infer the return type from the `pageFunction` you provide. If it is unable to, you can use the generic type to tell the compiler what return type you expect from `$$eval`:
|
|
|
|
## Example 3
|
|
|
|
```ts
|
|
// The compiler can infer the return type in this case, but if it can't
|
|
// or if you want to be more explicit, provide it as the generic type.
|
|
const allInputValues = await page.$$eval<string[]>(
|
|
'input',
|
|
(elements: HTMLInputElement[]) => elements.map(e => e.textContent)
|
|
);
|
|
```
|