diff --git a/docs/api/puppeteer.elementhandle.__eval.md b/docs/api/puppeteer.elementhandle.__eval.md index db2db5c1..f31a5299 100644 --- a/docs/api/puppeteer.elementhandle.__eval.md +++ b/docs/api/puppeteer.elementhandle.__eval.md @@ -54,7 +54,7 @@ HTML: JavaScript: -```js +```ts const feedHandle = await page.$('.feed'); expect( await feedHandle.$$eval('.tweet', nodes => nodes.map(n => n.innerText)) diff --git a/docs/api/puppeteer.frame.__eval.md b/docs/api/puppeteer.frame.__eval.md index 2d0034b7..456e3ca9 100644 --- a/docs/api/puppeteer.frame.__eval.md +++ b/docs/api/puppeteer.frame.__eval.md @@ -43,6 +43,6 @@ A promise to the result of the function. ## Example -```js +```ts const divsCounts = await frame.$$eval('div', divs => divs.length); ``` diff --git a/docs/guides/request-interception.md b/docs/guides/request-interception.md index 0b4a50a7..23c6a69f 100644 --- a/docs/guides/request-interception.md +++ b/docs/guides/request-interception.md @@ -5,7 +5,7 @@ continued, responded or aborted. An example of a naïve request interceptor that aborts all image requests: -```js +```ts import puppeteer from 'puppeteer'; (async () => { @@ -47,7 +47,7 @@ block. Always execute `request.isInterceptResolutionHandled` and This example demonstrates two synchronous handlers working together: -```js +```ts /* This first handler will succeed in calling request.continue because the request interception has never been resolved. */ @@ -68,7 +68,7 @@ page.on('request', interceptedRequest => { This example demonstrates asynchronous handlers working together: -```js +```ts /* This first handler will succeed in calling request.continue because the request interception has never been resolved. */ @@ -110,7 +110,7 @@ synchronously before using `abort/continue/respond`. Here is the example above rewritten using `request.interceptResolutionState` -```js +```ts /* This first handler will succeed in calling request.continue because the request interception has never been resolved. */ diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 093e5917..501dc74e 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -3,8 +3,7 @@ :::caution Chromium currently does not provide arm64 binaries for Linux. There are only -binaries for -[Mac ARM with experimental support from Puppeteer](https://pptr.dev/contributing#macos-arm-and-custom-executables). +binaries for Mac ARM. ::: diff --git a/packages/puppeteer-core/src/api/ElementHandle.ts b/packages/puppeteer-core/src/api/ElementHandle.ts index 3355c5ce..e302ba1a 100644 --- a/packages/puppeteer-core/src/api/ElementHandle.ts +++ b/packages/puppeteer-core/src/api/ElementHandle.ts @@ -443,7 +443,7 @@ export abstract class ElementHandle< * * JavaScript: * - * ```js + * ```ts * const feedHandle = await page.$('.feed'); * expect( * await feedHandle.$$eval('.tweet', nodes => nodes.map(n => n.innerText)) diff --git a/packages/puppeteer-core/src/api/Frame.ts b/packages/puppeteer-core/src/api/Frame.ts index 4e2fca1a..394d1915 100644 --- a/packages/puppeteer-core/src/api/Frame.ts +++ b/packages/puppeteer-core/src/api/Frame.ts @@ -604,7 +604,7 @@ export abstract class Frame extends EventEmitter { * * @example * - * ```js + * ```ts * const divsCounts = await frame.$$eval('div', divs => divs.length); * ``` *