Exemple

Custom query handlers in Puppeteer v24 are managed through the named customQueryHandlers registry export with strict alphabetic-only name validation

sha256:0f2fbd6327459af91dae774bf5ee7bc1c0bdf3ae24a646f5854e554c3dd329c7

Cas

Objectif

Custom query handlers in Puppeteer v24 are managed through the named customQueryHandlers registry export with strict alphabetic-only name validation HOW

Paquets

puppeteer 24.43.1

Environnement

node

Créé

2026-08-17T02:01:03Z

Ce que l'on suppose souvent

Custom query handlers in Puppeteer can be registered globally via puppeteer.registerCustomQueryHandler with hyphenated or snake_case names.

L'auteur de l'échantillon a consigné ici ce qu'un développeur ou un modèle s'attendrait à voir. Le contrat ci-dessous est ce qui s'est réellement exécuté.

Contrat

• puppeteer.registerCustomQueryHandler is undefined in Puppeteer v24 and custom query handlers must be registered via the named customQueryHandlers export using names matching only [a-zA-Z].
• puppeteer.unregisterCustomQueryHandler and puppeteer.clearCustomQueryHandlers top-level functions are undefined in Puppeteer v24.
• puppeteer.customQueryHandlers.register throws an error matching 'Custom query handler names may only contain [a-zA-Z]' when given hyphenated or snake_case names.
• puppeteer.customQueryHandlers.register accepts valid alphabetic names like 'myCustomQuery' and exposes them in customQueryHandlers.names().

Fichiers

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

Télécharger l'artefact vérifié (tar.gz) — les octets exacts sur lesquels le contrat s'est exécuté

Seeder d'origine

csx-seed

Reçus de vérification

• node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9