At Smartagent, we faced a challenge that might sound familiar to many developers: our client-side PDF generation feature was struggling under the w...
For further actions, you may consider blocking this person and/or reporting abuse
One of my clients wanted PDF generation and we realized: literally just
window.print()does this. Saved us probably months of development time and architectural heartache.yes but sometime we need assembled data
@media print
Wtf. Why you are generating PDFs on the frontend, not backend? Especially for 22k rows. I understand you send those rows to the client? My god.
"this approach would require us to rewrite our entire PDF generation logic a daunting task "
Yes, because you made a mistake in the beginning. Honestly you should get it straight ASAP. Those PDFs were generating for at least 30 seconds, and im sure you had a lot of time previously to tackle that problem.
The solution is cool though, anyway
client side loading 22k rows, chances are high of rendering a users machine unusable while it's processing the PDF, isn't that going to affect user experiences?
tanstack table handles this in very good way, it has virtualization and other UI related optimization and obviously, we use pagination!
I believe @j0nimost is talking about pdf-creation & rendering.
In a web-worker, it takes longer than the main thread but we didnt face that issue. Phones did heat up though...
lol 😂, i can imagine it on older laptops 4th gen intel laptops with 4GB ram, or tablets.
From my own experience I can confirm that frontend client side web worker solution is the way to go.
You talked about 22k rows. How much time did 22k rows take?
It must have taken longer time.
I thought 22 is a smaller number :|
Well ofcourse watson.
Thanks for sharing!
What wasm pdf library did you use?