linkedom VS browserless

linkedom is your answer

linkedom - to parse HTML into a workable DOM. I used to use jsdom, but I switch for performance reasons.

For simple scraping where the content is fairly static, or when performance is critical, I will use linkedom to process pages.

https://github.com/WebReflection/linkedom

When the content is complex or involves clicking, Playwright is probably the best tool for the job.

https://github.com/microsoft/playwright

I recently started using linkedom for this and it has been an absolute joy

This looks great. I wonder how it compares to linkedom (repo[1], writeup[2]), which I have found to be fantastic.

[1]: https://github.com/WebReflection/linkedom

[2]: https://webreflection.medium.com/linkedom-a-jsdom-alternativ...

linkedom, fastest, but lacks essential features

Other things to do would be to use linkedom instead of JSDom, look into a better assertion library than assert etc.

Sounds somewhat similar to linkedom[1], which performs nicely.

[1]: https://github.com/WebReflection/linkedom

The core product is managed, cloud hosted browsers. We run thousands at a time using AWS and DigitalOcean, for people to use with Puppeteer and Playwright scripts. Our container is also available to self deploy under an open-source license.

You should search for "Puppeteer as a service", there are some projects on github that you could deploy such as https://github.com/browserless/chrome

So I recently installed ChangeDetectioIO on my server, it requires either selenium/standalone-chrome-debug:3.141.59 or browserless/chrome. I installed it with Selenium in a docker container since I noticed that it was running better than the browserless/chrome service.

I had a look to this one: https://github.com/browserless/chrome ... but it is not suitable for builds, e.g. set to production mode, user permissions and so on.

git clone https://github.com/browserless/chrome /opt/browserless