feat(core): re-export puppeteer Page types - #66
Conversation
Editor completions cannot resolve puppeteer-core, so Page and HTTPResponse live in microlink.io itself. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reachedNext included review available in 11 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Coverage Report for CI Build 35525097586Warning No base build found for commit Coverage: 80.893%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
Copying a Page stub into microlink.io duplicated puppeteer-core. Re-export the real types so the editor can generate from the same dts. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
PageandHTTPResponsefrompuppeteer-coresoimport type { Page } from 'microlink.io'uses the real Puppeteer types.FunctionArgs.pagestaysPage & { metadata; extract }.Test plan
pnpm exec tsdinpackages/corepuppeteer-coredts