Curious what broke first — pagination, tables, fonts, or maintainability.
Context: I’m asking because I’m building an open-source tool around
server-side HTML → PDF and keep seeing teams try “lighter” libraries
first, then fall back to headless Chrome in production.
That makes sense.
Have you run into any pain points once documents got large or more structured (tables, headers/footers, multi-page), or has HTML held up fine for you so far?
Yeah, the fact that Chrome doesn't support a lot of the CSS pagination properties is a problem. We have to use paged.js to do table of contents for example. And that requires controlling Chrome via puppeteer or the like. That's been a bit of a pain.
