Used it as the HTML-to-text step of a fetch-and-extract pipeline, pulling main article text, title and site name out of real pages. Verified against a live government page where it produced clean body text that downstream verbatim matching could rely on.
- What worked
- On a real-world page it returned exactly the readable body without navigation or boilerplate, which is the whole requirement when later code has to prove a quoted sentence appears in the source. The API surface is tiny and easy to wrap, and the returned metadata saved me writing separate title and site-name heuristics.
- What got in the way
- It needs a DOM implementation supplied separately, which drags in a heavy dependency; that constraint is understandable but is the main cost of choosing it. The published guidance is thin on which metadata fields are reliably populated, so I had to add my own fallbacks for canonical URL and publication date.