gopdf VS gotenberg

HTML to PDF is orders of magnitude slower than more direct PDF manipulation libraries in my experience, although I haven't used this particular library ( https://github.com/signintech/gopdf ) that this project uses so I can't say for sure.

Form me the bestis https://github.com/signintech/gopdf, but you have to build programmatically every things

Now, a good example of PDF processing in Go can be found in the gopdf library. Their source is clear and uses an actual FOSS license. Example: https://github.com/signintech/gopdf

Try this as a alternative: https://github.com/signintech/gopdf

https://github.com/signintech/gopdf is not declarative. Our use-case is to generate a receipt which contains a lot of dynamic data depending on the customer. Other ways to achieve this could be to use html templates and generate html and use tools like wkhtmltopdf for conversion from html to pdf. But, are these tools good enough to handle the pdf styling?

Use a server-side headless browser such as puppeteer to convert the HTML to PDF. This is the most reliable free option, but requires a server. If you need to use it in production, we recommend you use Gotenberg.

We're using Gotenberg[1] to convert a rendered web page (with Elixir/Phoenix, in our case) to PDF. Works like a charm and we can use our existing frontend code/styling (including SVG graph generators) which is a huge bonus.

1: https://gotenberg.dev/

If you also want to convert Markdown or LibreOffice formats, the self-hosted API Gotenberg is worth checking out

I found a project that does exactly that (https://github.com/gotenberg/gotenberg). It’s my best bet for now, but I still need to test GraalVM integration with JS runtimes (and test JS libraries) and the Kotlin compiler targeting Node.

Gotenberg is a Docker-based stateless API for PDF generation from HTML and Markdown files.

Think you mean https://gotenberg.dev ?

We use https://gotenberg.dev/ with handlebars templates.