Topics created by fhrtms

But in the inline script to parse the DOM i can't use new Buffer.from(title, 'utf8').toString('base64'). I can only use atob/btoa there.

Yes, true, that didn't come to my mind.

What is the meaning of the notation item@@@...@@@?
Is this somehow processed differently?

Yes, this is our internal mark, which pdf utils remove during post-processing and from the information builts $pdf.pages.items collection you typically use during the merge operations.

I've spent some time analyzing the options we have for improving the ToC, but I didn't find some breaking ideas to make things easier for you.

I'm not sure creating ToC from DOM is the right way to go, but I at least added the official example to the documentation for rendering ToC without the previous declaration and with ToC position directly in the main template.
https://playground.jsreport.net/w/admin/tV6sVKbV
This was triggered by ideas in this thread. Thank you

With npm i ghostscript-node i get a valid PDF.

const gs = require("ghostscript-node"); async function afterRender(req, res) { // load PDF as Buffer const pdf1 = await downloadPDF('https://www.aubrete.lt/wp-content/uploads/2019/06/1-COVERSTYLE-1.pdf') // get number of pages of pdf1 const numPagesPDF1 = await gs.countPDFPages(pdf1); // get Buffer object with bytes of specified set of pages // page numbers begin with 1, last page is included const partOfPDF1 = await gs.extractPDFPages(pdf1, 1, numPagesPDF1); // checks if pdf1 is a valid PDF file const isPDF1Valid = await gs.isValidPDF(pdf1); if(isPDF1Valid) { res.content = await jsreport.pdfUtils.append(res.content, partOfPDF1) } }

I' m glad you like what we do.

The opts.fn evaluate handlebars inside the block helper and returns a string. The opts.inverse does the same, but for the block you put into the {{else}} section.
Documentation:
https://handlebarsjs.com/guide/block-helpers.html

Your solution looks good, you can even go just with
innerhtml: opts.fn(this)