Posts made by Kishan-Talaviya-TBS

Thank you

Hii,

Just checking in — as mentioned earlier, the fix was in master, and a release was expected within a couple of weeks.

Is the release now scheduled, or do you have an updated ETA for the new version?

Hi Jan,
Thank you for the update and for isolating the issue—appreciate you sharing the details around the Chromium behavior and the AWS Lambda limitations.
Understood that the approach is being reimplemented and that further analysis is still ongoing. To help us plan our rollout and dependency upgrades on our side, could you please let us know if there is a tentative target timeline or expected window for the next jsreport release that may include this fix?

Thanks again for your continued support. Looking forward to your guidance.

Hi,
We have successfully resolved the AWS Lambda layer size issue by separating Chromium and jsReport into two different layers, and the setup is now deploying and running correctly.
PDF generation using Chromium is working as expected. However, we are currently facing an issue specifically with the html-to-xlsx recipe.

Issue Details:
When executing the html-to-xlsx recipe, the Lambda function fails with the following error:
Error: Protocol error (Browser.getVersion): Target closed

This error occurs during Chromium initialization and causes the Lambda invocation to fail.

Chromium Launch Configuration
We are launching Chromium using @sparticuz/chromium with the configuration.

Additional Notes

• AWS Lambda runtime: Node.js with 24.x runtime
• Chromium is provided via a separate Lambda layer. Memory size: 1024 MB
• PDF recipes work fine with the same Chromium setup
• The issue only occurs with the html-to-xlsx recipe
• We are using @sparticuz/chromium version 143.0.0.

Could you please help with this?