Ask HN: What made you move back to HTML-to-PDF in production?
6 pointsby gokulsiva25 days ago3 comments
  • baggy_trough25 days ago
    I only know how to lay things out well in HTML, so I never moved away from it.
    • gokulsiva25 days ago
      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?
      • baggy_trough25 days ago
        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.
        • gokulsiva25 days ago
          Yeah, that matches my experience too — Chrome gets you ~80% there, but the missing pagination primitives push you into extra layers like paged.js.

          I’ve also hit issues with tables and page breaks.

          Curious if TOC was the main blocker for you, or if there were other cases where Chrome alone didn’t hold up.

          • baggy_trough24 days ago
            That's really the main one I remember.
  • TheCapeGreek24 days ago
    I've never found any lib or tooling (in my ecosystem) that DIDN'T use html -> pdf
  • gokulsiva25 days ago
    [dead]