hmm i still see the wrong path in the error node_modules\puppeteer.local-chromium

hi! i'm not 100% sure but it seems that the path here C:\dist\win-unpacked\resources\app.asar\node_modules\puppeteer.local-chromium\win64-800071\chrome-win\chrome.exe ENOENT. is wrong, it seems it should be C:\dist\win-unpacked\resources\app.asar\node_modules\puppeteer\.local-chromium\win64-800071\chrome-win\chrome.exe, the difference is puppeteer\.local-chromium. maybe you are setting that path in wrong way, check that this part of code is setting the correct path.

// get correct path to chrome executable when running on compiled electron app
  process.env.extensions_chromePdf_launchOptions_executablePath = path.join(CWD, chromePath.slice(chromePath.indexOf('node_modules')))

hi! unfortunately, the html-to-xlsx recipe does not support images yet, hopefully, we will add it soon, see this issue to keep track of the progress

hi! the way to do the if/else of the template depends on the template engine that your report uses, for example, if it is handlebars you can do it like this. I suggest always looking at the specific template engine docs to know how to define something in the template

so we solve this internally via email. the problem was that #xlsxAddImage was not receiving different image name per each iteration of the loop

hi! hmm that part of your code seems to be fine, however maybe the issue can be somewhere and in that case, we need the full context of the report, maybe you can upload the problem to the playground and we can check it.

hi @zewar96

yes the download from the embedded viewer does not work, this is because of the nature of the dynamic pdf, if you want to save the report, click the download button that is inside the "Run" button of studio toolbar.

hmm sorry still have doubts about how you render the preview, it seems you are sending an http request, right? what do you do with the response? how is that rendered in your html/app? that is critical to know when having the display name in the preview

you can only require('jsreport-proxy') inside the script file, it is a "virtual" module because it only exists inside the script execution, it is not something published to npm so you can not access it outside of a script, you only need to have instance.use(require('jsreport-scripts')()); if want to have the jsreport-proxy suppor tin the scripts

hi!

how are you handling the preview? is this jsreport studio? or a custom pdf preview in your app?