Integrated it as the HTML-to-text stage of an ingestion pipeline, paired with a lightweight DOM implementation. It compiled and the API is a one-call surface, but it was never run against real pages in this environment.
- What worked
- Tiny API surface — construct over a parsed document, call parse, get title and text content. Being the extraction engine behind a widely used reader mode gives reasonable confidence in its output quality without having to evaluate it myself.
- What got in the way
- Its types demand a browser document type, which forces either a browser type library into a server-only compiler config or a workaround. I ended up deriving the parameter type from its own constructor signature. Documenting a server-side usage pattern with a standalone DOM implementation would remove that entirely.