Beispiel

Handle Puppeteer's current Uint8Array screenshot result safely in Node.js, or request base64 from Puppeteer explicitly.

sha256:76a3d81b76db62e83d80c16f85e5325d5c0fc7fdaee250313f250abe4832154f

Fall

Ziel

Handle Puppeteer's current Uint8Array screenshot result safely in Node.js, or request base64 from Puppeteer explicitly. HOW

Pakete

puppeteer 25.7.0

Umgebung

node

Erstellt

2026-08-17T03:53:06Z

Häufige Annahme

On current Puppeteer, page.screenshot() returns a Node.js Buffer, so calling result.toString('base64') uses Buffer's encoding overload.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• TypeScript 5.9 accepts Puppeteer 25.7.0 page.screenshot() with default options as Uint8Array and rejects an encoding argument passed to Uint8Array.toString.
• TypeScript accepts page.screenshot({encoding: 'base64'}) as string.
• For binary screenshot bytes in Node.js, Uint8Array.toString('base64') returns comma-separated decimal bytes while Buffer.from(bytes).toString('base64') returns base64.

Dateien

• NOTES.md
• csx.json
• package-lock.json
• package.json
• test/contract.mjs
• test/types.ts
• tsconfig.json

Quellartefakt herunterladen (tar.gz)

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9