GoQuery VS chromedp

Your comment was posted 4 minutes ago. That means you still have enough time to edit your comment to change it so it contains real URLs:

<https://github.com/PuerkitoBio/goquery>

<https://github.com/dop251/goja>

(Please do not reply to this comment—I won't be able to delete it once the previous post is fixed if it contains replies.)

How about - https://github.com/PuerkitoBio/goquery

Assuming you're asking about https://github.com/PuerkitoBio/goquery , to interpret your printout you want to look at what Find is defined to return, a *Selection. https://github.com/PuerkitoBio/goquery/blob/39fb6d4dc47a07e5782494b6defc89a194b1f906/traversal.go#L23

github.com/PuerkitoBio/goquery - library that provides a convenient and concise way to query HTML and XML documents. It provides a jQuery-like API for selecting elements and extracting data, making it a popular choice for web scraping in Go.

Yep, I thing I can add it. Add new goquery alternative will be good :)

If I want to parse the structure of HTML and not interact with it from a browser point of view, I use this in Go: https://github.com/PuerkitoBio/goquery

goquery

I had a similar problem that I solved with goquery and otto. You can use goquery to traverse the DOM and otto to execute the script fragment. Then just grab the data from otto's VM.

Your scraping being slow and using Chrome might be a blessing in disguise though. If you aren't careful you can get detected as a bot and banned from the site.

https://github.com/PuerkitoBio/goquery

If you're willing to add constraints around the goal, you can catch this type of error with semgrep rules and/or unit tests using qoquery.

RUN go get github.com/PuerkitoBio/goquery

There are a billion things that you need to consider when building a decent web crawler, especially interacting with pages in the modern web. For example, a lot of content is dynamically loaded by the browser nowadays, and won't show up if you make a simple HTTP request. Open your browser devtools and look at the network tab after you make a request, and you'll see it makes loads of auxiliary requests. Some content is also only loaded after you interact with it (e.g. hover, click). For that reason I'd recommend using something like chromedp and do browser based crawling, even if it's much slower.

You could use something like the chrome dev tools (https://github.com/chromedp/chromedp) or look into JS runtimes in Go and try to handle the I/O yourself.

Thanks. I've found Chromedp [0] to be a good Selenium replacement when programming in Go. Used in conjunction with HeadlessShell [1] you can deploy a Go app into a container and do the testing all within the same container with low overhead.

[0] https://github.com/chromedp/chromedp

Is it node specific? Could you just use https://github.com/chromedp/chromedp and run it as an actually webpage and get the value from that?

It looks like https://github.com/chromedp/chromedp is the most popular option. There's also https://github.com/playwright-community/playwright-go. Any thoughts or advice about using these tools?

The alternative is to drive, for example, Chrome with the DevTools protocol (using something like https://github.com/chromedp/chromedp or https://github.com/raff/godet (this is my version of a DevTools driver).