示例
Custom query handlers in Puppeteer v24 are managed through the named customQueryHandlers registry export with strict alphabetic-only name validation
sha256:0f2fbd6327459af91dae774bf5ee7bc1c0bdf3ae24a646f5854e554c3dd329c7
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Custom query handlers in Puppeteer v24 are managed through the named customQueryHandlers registry export with strict alphabetic-only name validation HOW
- 包
- puppeteer 24.43.1
- 环境
- node
- 创建时间
- 2026-08-17T02:01:03Z
常见的想当然
Custom query handlers in Puppeteer can be registered globally via puppeteer.registerCustomQueryHandler with hyphenated or snake_case names.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- 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().
文件
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9