Posts made by admin

Thank you for the template. We're gonna check if we can optimize processing a bigger XLSX template like this one
https://github.com/jsreport/jsreport/issues/1270

We will again update puppeteer/chromium in the next release. As always. Likely soon.

If you need to update just now, go ahead and update the puppeteer dependency.
You just need to list the latest puppeteer dependency in your package.json.

Or build your own Docker image with the updated Chromium. However, note that the latest Chromium with the fix is not yet in the public repository at the time of writing this post.

Unfortunately, this isn't supported yet.
I've added this feature to the backlog now
https://github.com/jsreport/jsreport/issues/1269

Yes, thanks. Done...

Hi,

Unfortunately, we don't provide a compiled version of jsreport in the latest release. There is a problem with the technology used for compilation. We will try to support the compiled versions again in the next release.

I've updated the release notes. I apologize for the confusion.

Jan

Unfortunately, it's not there. There was some controversy, but I am adding this now...

The dependencies will be updated with the next release as always.
https://github.com/jsreport/jsreport?tab=readme-ov-file#vulnerabilities

The release is scheduled for this week.

Yes, you can use a custom jsreport script where you can code what you need
https://jsreport.net/learn/scripts
https://jsreport.net/learn/pdf-utils#usage-in-script

const jsreport = require('jsreport-proxy')
async function afterRender (req, res) {
    res.content = await jsreport.pdfUtils.merge(res.content, Buffer.from(req.data.externalPdf, 'base64'))
}

Full demo here
https://playground.jsreport.net/w/anon/2lCyXIBl

It works the way jsreport takes your html as is and puts it into the docx file source.
When you open the Word app, it interprets the HTML.
jsreport does not influence how it is interpreted.

Perhaps you can try the docx recipe and docxHtml helper, if you need to display just a simple html.
This would let you modify the page size and orientation in the word template.
https://jsreport.net/learn/docx#docxhtml

Maybe you can implement your own helper "dynamicComponent" that receives the component code and returns the evaluated result.
It would be up to you where you download the component implementation.

https://playground.jsreport.net/w/anon/CQZ_3bC4

const jsreport = require('jsreport-proxy')

async function dynamicComponent(content, helpers) {
    return await jsreport.templatingEngines.evaluate({
      engine: 'handlebars',
      content: content,
      helpers: helpers,
      data: this
    }, {
      entity: jsreport.req.template,
      entitySet: 'templates'
    })
}

{{{dynamicComponent "some dynamic content {{myData}}" "function aHelper() {}"}}}

The custom users need to be persisted.

However, you can create a startup script that will import or create them.

See this config
https://jsreport.net/learn/configuration#workers
https://nodejs.org/api/worker_threads.html#worker_threads_worker_resourcelimits

Could you please let us know the default heap size?

These are the runtime/nodejs settings.
Each thread gets the same default limit as the main thread
~1.5 GB on 64-bit systems

How many percentage of RAM should be allocated to heap?

There is no rule of thumb, try what works best for you.
The main thread can remain in default, and the rest can be divided among workers.

If we have set only one worker then why are we getting heap size limit issue?

Because every worker has the nodejs default limit.

Do references held by previous renders get freed up after report rendering finishes?

nodejs is the garbage-collected runtime. So it gets cleaned from memory when the GC gets triggered by the runtime.

Hi, it is likely that in June 2026, the node VM module will enable us to sandbox ESM modules.

However, note that in the newer node, you will still be able to use CommonJS modules as of now.
In other words, that date, June 2026, shouldn't be significant for you.

This hasn’t been implemented yet, unfortunately — there were other priorities.

The xlsx recipe, when you use xlsxAdd, already use batching and streaming internally.
Do you hit an OOM error when having many rows?

Would you be able to email me the mentioned pdfs?

You can send the export or compressed data folder...

I cannot imagine why the perf would be different when using external config. Maybe some kind of disk virtualization/docker/os issue.

Anyway, what if you test things without Docker first and then troubleshoot the containerization issues?

You have two loops in your folder structure.

folder with shortid 0HYiJb9 has parent itself
folder AKH3fuS has a parent 2vof8k_ which has parent AKH3fuS

To fix your workspace
set to the folder with shortid: 0HYiJb9 the prop folder null to move it to the root
and set to the shortid: 2vof8k_ the prop folder to null

I am not sure how this happened. If you will ever be able to deterministically replicate this, we will happily take a look.

why handlebar and chrome pdf took this much of time , any idea ?

The only thing that comes to my mind is that the reason is a super throttled CPU.
Try a different machine, or send me your workspace I can test.

There is no extra setting. Try to compare the profile, what is actually the bottleneck
https://jsreport.net/learn/studio#profiles

Regarding the original question...
It appears that the studio's JavaScript is freezing the browser. Would it be possible for you to share with me confidentially your workspace? An export or a mongodb dump. You could clean all the data and template content if you need to. You can email me a link where to download it to jan.blaha@jsreport.net

Regarding rendering time...
The jsreportonline has limited containers, so your full machine env should actually be faster.
One thing that comes up to my mind is that the problem could be amount of entities -> slow db and loading.
Could you check your collections have indexes? The latest jsreport automatically creates indexes.