Topics created by Ish Modi

If the height of the component is fixed, then this demo should work for you
https://playground.jsreport.net/w/admin/Ci3l8_UQ

The config will stop the server hard part work, but the studio will keep those harmless ping requests. Any problem with that?

Have you checked the note here? The jsreport 4.3.0 has the updated chrome...
https://github.com/jontewks/puppeteer-heroku-buildpack?tab=readme-ov-file#important

Unfortunately no. There is no extra config to reduce memory usage in pdf utils or chrome.

However, you can try to limit the number of workers with workers.numberOfWorkers=1

Try the following
https://stackoverflow.com/a/55090914/1660996

You need to configure your web server/nginx properly.
https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/
https://medium.com/@svsh227/error-413-request-entity-too-large-in-nginx-with-client-max-body-size-changes-in-nginx-6aacd525fe11

@Ish-Modi it all depends on the pdf viewer you use, in the studio we use the standard pdf viewer which has the limitation I described.

in your app, you don't need to use the same pdf viewer, although it is handy to let the browser handle the preview, it will have the same limitation. instead, you can check other pdf viewers which allow this customization. I think pdf.js is one of those that don't have this problem and will let you have a download button with a custom name. another solution is to add to your app a custom download button that triggers download from jsreport-client.