Topics created by orenww

Perhaps you can select just what pages you want and render multiple times.
This can be done using "pageRanges" option

You are trying to mix chrome native headers with the pdf utils which won't work.

I would recommend first installing full jsreport locally. Open the studio and fiddle with it to understand how it works. Only then get to your app and try to replicate the same using API calls.

The key on how to use the pdf utils from the API calls without storing templates is at the end of the docs
https://jsreport.net/learn/pdf-utils#api

The request could in the end looks something like this

{ "template": { "content": "some pages in main", "recipe": "chrome-pdf", "engine": "handlebars", "chrome": { "marginTop": "50px" }, "pdfOperations": [{ "template": { "content": "{{#each $pdf.pages}}.. {{/each}}", "recipe": "chrome-pdf", "engine": "handlebars" }, "type": "merge", "mergeWholeDocument": true, }] } }

We have some notes for developing with VS code here if you are interested
https://jsreport.net/blog/debug-jsreport-in-vscode

Is a recommended way to package node project that include jsReport to exe?

If it's not aboslutely necessary for your deployment, I wouldn't go that way.

I couldn't understand from the above link what should I do?

If you git clone jsreport repo, install it and then run yarn compile, it will compile the current jsreport app using pkg into exe. Its a complicated process which I won't go into details, but if you are in need, you can study the whole flow from the code.

In previous projects (without jsReport) I used "pkg" and it worked well.

jsreport includes also binary dependencies and dynamic imports so things aren't that simple and pkg doesn't work out of the box. It needs several tweaks to make it working.

The child template requires the template to be stored in the template store. So it typically requires you to start jsreport studio and define your workspace.