![]() Some libraries use Chrome's HTTP endpoints, like /json to inspect debug-able targets, which browserless also supports. Once the session is done then it closes and awaits for more connections. When a websocket connects to browserless it invokes Chrome and proxies your request into it. Support for running and development on Apple's M1 machinesīrowserless listens for both incoming websocket requests, generally issued by most libraries, as well as pre-build REST APIs to do common functions (PDF generation, images and so on).Error tolerant: if Chrome dies it won't.Configurable session timers and health-checks to keep things running smoothly.An interactive puppeteer debugger, so you can see what the headless browser is doing and use its DevTools.Docker image's are labelled with information on the version of Chrome, V8, webkit and more.Docker releases that are built for specific puppeteer versions.Debug Viewer for actively viewing/debugging running sessions.Fonts and emoji's working out-of-the-box.Parallelism and queueing are built-in and configurable.If you've been struggling to get Chrome up and running docker, or scaling out your headless workloads, then browserless was built for you. We even handle edge-cases like downloading files, managing sessions, and have a fully-fledged documentation site. ![]() On top of all that it takes care of other common issues such as missing system-fonts, missing external libraries, and performance improvements. It offers first-class integrations for puppeteer, playwright, selenium's webdriver, and a slew of handy REST APIs for doing more common work. Browserless is a web-service that allows for remote clients to connect, drive, and execute headless work all inside of docker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |