feat(community): Add support for connecting to remote browser via Websocket

[mikiastilahun]

Pull Request: Connect to an Existing Browser Instance

Summary

This PR introduces functionality to connect to an already running browser instance instead of launching a new one each time. This is particularly useful for users who have a separate Chrome instance running and prefer to connect to it directly for efficiency and custom workflows.

Key Features

• Connect to an existing browser: Avoids the need to launch a new browser process every time.
• Streamlined workflows: Ideal for scenarios where a persistent browser session is managed externally.
• Performance benefits: Reduces overhead by reusing an already running instance.

Use Case Example

• A user has a Chrome instance running with specific configurations and wants to connect to it without starting a new browser instance.

---

Contributor:
Twitter/X: @Mike_T_Abebe

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
langchainjs-docs	🛑 Canceled (Inspect)			Jan 30, 2025 0:26am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
langchainjs-api-refs	⬜️ Ignored (Inspect)			Jan 30, 2025 0:26am

[jacoblee93]

Seems good to me, thank you!

[jacoblee93]

Could you run yarn format?

[jacoblee93]

I got it nvm

[jacoblee93]

Getting some build errors:

src/document_loaders/web/puppeteer.ts(73,33): error TS2339: Property 'browserWSEndpoint' does not exist on type 'PuppeteerLaunchOptions'.

[mikiastilahun]

The browserWSEndpoint is actually in the PuppeteerLaunchOptions, Let me update the typings and push