3 ms·
My question on these is always how it handles multi page documents. Most DOM and CSS approaches to HTML to PDF require it to fully render everything for placeme
by brightball 6y ago
My question on these is always how it handles multi page documents. Most DOM and CSS approaches to HTML to PDF require it to fully render everything for placement before it can convert.
If you have to render something big, like a 300 page member directory for example, the approach will blow up.
- idreyn 6y agoI used paged.js in production and while it's definitely not fast enough to run during an HTTP request, it can render a 300 page document reasonably quickly, definitely within the 120 second TTL of our worker tasks. It can be quite finicky though and sometimes stalls on things like images that are taller than a single page.
- brightball 6y agoThe RAM upper limit is my bigger concern.
- julientaq 6y agowww.booksprints.net people made 700 pages (which makes a lot of div to handle and process) without too much issues. And you can also check https://villachiragan.saintraymond.toulouse.fr/impression https://villachiragan.saintraymond.toulouse.fr/impression to see HD images. Both went straight to the printshop.