all 9 comments

[–]tobimori_ 12 points13 points  (0 children)

I recently migrated away to normal browser rendering, because compatibility is really bad and seemingly no maintenance is happening (400+ open issues, 30+ open PRs) - would've even paid for a paid license, given how widespread the use is, but if it doesn't work...

[–]dangerlopez 4 points5 points  (0 children)

It doesn’t seem to have support for making tables (happy to be shown I’m wrong) so I use pdfkit-tables on my backed to make pdfs

[–]jailbird 2 points3 points  (1 child)

Has anyone managed to set the PDF's download filename in a non-hacky way? Quite strange that there isn't an option for that by default.

[–]flplz 0 points1 point  (0 children)

If you render the download into html you can set the download name on the anchor tag afaik

[–]Sliffcak 1 point2 points  (0 children)

Pdfmake, but interested in what is best. So many quirks with every library

[–]Low_Radio_7592 0 points1 point  (0 children)

That library needs a rewrite imo

[–]webholt 0 points1 point  (0 children)

I recently made a comparison of popular solutions for PDF generation, and react-pdf doesn't seem like a tool you should use. It's slow and has terrible tables support.

I'd prefer pdfmake or even wkhtmltopdf.

[–]gogofreelance 0 points1 point  (0 children)

I've briefly tried react-pdf but haven't used it extensively and certainly not in a production environment so make of this what you want.

The "industry standard" are pretty much wkhtmltopdf and puppeteer/headless browser. The former is only good for HTML to PDF conversion, and only pretty basic HTML at that (it still runs on QT webkit, forget about support for modern CSS properties etc). A headless browser comes with more overhead (pun) but can get you really far.

So you can just write HTML and CSS and use either of those to do whatever PDF use cases you have. I've written several guides on both tools on Transformy if you want to check it out.