Version 3.13 and jsreport-electron-pdf in Fargate

jeffbonasso-ambifi

I am currently using JSReport Online which seems to use Version 3.13 of JSReport. I have a lot of reports using Electron that will take quite a while to migrate. I have a customer where I can't use JSReport Online anymore so trying to deploy to Fargate. I have 3.13 running but missing the Electron PDF recipe. I have tried installing multiple ways but keep getting...

-- error (1) --
-> stack
Error: Error when loading extension electron-pdf@3.2.0
Error: Extension "electron-pdf" is not compatible with "core" extension. Missing ".requires" information in "electron-pdf" definition
    at validateMinimalVersion (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/validateMinimalVersion.js:24:11)

Any thoughts or instructions how to install this extension?

admin

These versions work for me together... On windows, not sure how on Fargate

"@jsreport/jsreport-electron-pdf": "4.0.0",
"jsreport": "3.3.0",
"electron": "1.6.6"

Doesn't the chrome-pdf give you similar output as the electron-pdf?
We will have to remove electron from the jsreportonline this year anyway because otherwise we can't go further with the service.

jeffbonasso-ambifi

Thank you. I am now able to select the Electron PDF recipe! When I did a simple hello world test with it, it just hangs and times out. Any other configuration may be missing? Not yet deploying this to Fargate. Currently just testing directly in Docker image.

FYI- I have done some light testing switching to Chrome and looks promising, but some layout issues I see. A large number of reports, so for short-term trying to minimize effort if possible.

admin

You can see here how we solve the problem with running electron in docker
https://github.com/jsreport/playground-worker/blob/4.3.0/Dockerfile

Note the Fargate isn't able to run dockerized the new Chrome at this moment. It may change with the next Chrome version. However, it may easily end up, that Fargate hosts are missconfigured and can't run the latest Chrome, and we will have to wait until AWS or Chrome team fix it.
https://github.com/jsreport/jsreport/issues/1207