Posts made by SolunaSoftware

My problem may be related to this: https://forum.jsreport.net/topic/2713/jsreport-single-file-executable-exe-versioning-issue-need-stable-exe-version/4

and perhaps this (but I hope not 😯): https://social.msdn.microsoft.com/Forums/en-US/00ea29db-7e4c-4b46-ad25-4b3993832ac3/azure-function-app-windows-os-cannot-launch-chrome-via-puppeteerlaunch-chromium?forum=AzureFunctions

I do not known how to fix it. Please help. Thanks.

Thank you! I can confirm it works perfectly! 💪

When I test it, after my solution is deployed to Azure, it returns this error:

spawn UNKNOWNat ChildProcess.spawn (node:internal/child_process:413:11)at Object.spawn (node:child_process:700:9)at BrowserRunner.start (C:\home\site\wwwroot\node_modules\puppeteer\lib\cjs\puppeteer\node\BrowserRunner.js:119:34)at ChromeLauncher.launch (C:\home\site\wwwroot\node_modules\puppeteer\lib\cjs\puppeteer\node\ChromeLauncher.js:76:16)at async createBrowser (C:\home\site\wwwroot\node_modules\@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:98:26)at async allocateBrowser (C:\home\site\wwwroot\node_modules\@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:113:5)at async getBrowser (C:\home\site\wwwroot\node_modules\@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:23:30)at async module.exports (C:\home\site\wwwroot\node_modules\@jsreport\jsreport-chrome-pdf\lib\conversion.js:11:19)at async execute (C:\home\site\wwwroot\node_modules\@jsreport\jsreport-chrome-pdf\lib\chromePoolStrategy.js:20:22)at async C:\home\site\wwwroot\node_modules\@jsreport\jsreport-chrome-pdf\lib\lazyRecipe.js:61:20 {errno: -4094,code: 'UNKNOWN',syscall: 'spawn',logged: true,previousOperationId: 'bdjcmdtyp5aaqey'}

Any idea of what goes wrong?

👍 Thanks for quick response!

Hi

I wonder if jsreport can used without running it as a server.

In my case I have a backend (nest.js) with some api’s used by my frontend (quasar.js). My backend, when running locally on my machine, everything works just fine, using the jsreport package and initializing jsreport like this:

  static async init(port: number) {
    this._jsReporter = new jsreport.Reporter({
      httpPort: port,
      httpsPort: null, 
      authentication: {
        enabled: false
      }
    })

    this._jsReporter.init().then(() => {
      console.log('\x1b[32mReporter\x1b[0m is listening on port', this._port)
      this._ready = true
    })
  } 

and render reports like this:

if (this._ready) return this._jsReporter.render( { template: { … } } ) // Returns a PDF file
else { ... }

But when I deploy to Azure (as a Web App), my backend fails when calling jsReport.init(), with errors related to the port I use, it seems.

I wonder, if jsReport can be used without having it running as a Server, but e.g. just as function like this:

import * as jsreport from 'jsreport'

const options = { ... }
return jsreport.render( { template: { … } }, options ) // Returns a PDF file

Where no port in options are needed. That would be super simple (and cool).

Thanks for any advise.

Hi. jsreport looks great, but a few things is concerning me:

1. jsreport depends on deprecated code. E.g. puppeteer@16.1.0 and some other deprecated packages ('npm i jsreport' returns a handful critical vulnerabilities)
2. The package is huge (3.000+ files and 120 MB in size). Detailed package info can be seen : https://npmgraph.js.org/?q=jsreport

Are there any plan on addressing these issues?

Thanks!

That helped. Thanks!

Most of the time, saving entities in studio are not needed, to generate a report. That fooled me :-)

For scripts in global scope it seems not to work. For script in template scope works:

Thanks for quick reply. I'll will try the "extra script"-way and return with result.

Hi, how to enable the debug button in jsreport studio?

I'll like to see console.log(...) in e.g. a debug window or profile window: