docs(blog): add post on using Lightpanda as a remote browser - #4156
candidosales wants to merge 2 commits into
Conversation
Lightpanda exposes a CDP server, so PlaywrightCrawler and PuppeteerCrawler can use it through remotePlaywrightBrowserPool / remotePuppeteerBrowserPool. The guide covers the one-context-per-connection limit (maxOpenPagesPerBrowser: 1) and a RemoteBrowserProvider that starts one Lightpanda process per browser for per-browser proxies. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
barjin
left a comment
barjin
left a comment
There was a problem hiding this comment.
Thank you for the contribution @candidosales !
Having this in the official Crawlee guides means we'd need to keep this up to date. Since Lightpanda is a third-party project, I'd prefer to keep it out of the official docs.
Would you mind turning this into, e.g., a Crawlee blog post? See my (very similar) PR on Obscura support - perhaps you can draw inspiration from this?
Thanks again!
Lightpanda is a third-party project, so keep it out of the official guides and publish it as a community blog post instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
candidosales
changed the title
barjin
left a comment
barjin
left a comment
There was a problem hiding this comment.
Thank you @candidosales !
The post is good to go by me 👍 I'll keep this unmerged until Crawlee v4 is out - the examples could be confusing for users nowadays (current crawlee@latest is v3, which doesn't have the remote browser support).
There is no further action required from you, the post imo reads well. I'll update this PR once the v4 is out on npm as stable.
Cheers!
This branch has not been deployed
3 participants
Replaces #3481. Per review, moves the Lightpanda guide out of the official docs into a community blog post, since Lightpanda is a third-party project.
With the v4 remote browser support, Lightpanda works with the existing
PlaywrightCrawlerandPuppeteerCrawler. The post covers:remotePlaywrightBrowserPool()andmaxOpenPagesPerBrowser: 1. Lightpanda allows one browser context per CDP connection, so the shortremoteBrowser: { endpoint }form doesn't work.RemoteBrowserProviderthat starts one Lightpanda process per browser, since Lightpanda sets its proxy per process (--http-proxy).Tested against Lightpanda 0.4.1 with Playwright and Puppeteer.