Titouan Launay

Hi @homj! Could you provide your test document? Here is a sample test document that you can copy/paste in the playground. I have tested it right now and it seems...

Hi and thanks for the detailed explanation! These components will only work properly with the Fileforge renderer, however you should be able to achieve a somewhat similar effect with the...

Hi @ejscheepers, Some components will work perfectly fine with other renderers. For example, our Tailwind component will work fine, as will the Markdown or Latex ones. Components that tap into...

Hey @akshhack! Thanks for reaching out. This library is inspired by Resend's react-email available at https://react.email/ Let me know if this is what you are looking for!

Hey @EbubeEvan, could you confirm what version of `react-print-pdf` you are using? There have been improvements to running Tailwind server-side in the latest versions.

Hey @thebiltheory, thanks for these detailed examples! If using Onedoc as a backend, you don't actually need to run puppeteer as the payload is sent externally for rendering. This issue...

Makes sense, do you still use the tailwind component or has it been switched to plain css as well?

Note that the latest versions of react-print do work on Vercel, with the main caveat being that RSC (use client/use server) cannot be used. This is easy with the `pages`...

Hey @rivasdiego-dev, thanks for reporting this. We actually walked into a similar issue with our sandbox earlier today, where Vite treeshaking removes the React DOM dependency. Usually, adding `await import("react-dom/server")`...

Hey @ANYURU, thanks for the detailed walkthrough! Vite should handle bundling this gracefully, not sure why there are issues with Webpack specifically. It is likely being introduced by pdfjs-dist, but...