The v3 automatically migrates the old structured localization files into the new form.
Haven't you tried this path? The migration procedure creates new script that mocks the old behavior so you can continue using {{$localizedResource.myReportKey.title}} even its not recommended in the long term.
Do you think upgrading the chromium version would fix this issue?
It can be. The chrome performance fluctuates with different versions.
In our experience, it is getting even a little bit worse with new chrome versions.
If so, is there a plan to upgrade the puppeteer version jsreport is using in the near future?
Yes, we regularly update chrome to resolve security issues. But you can use the executablePath config to use the version you want.
There is no way to automatically collect and propagate all the entities the template uses.
You can either give the new user permission to read all entities.
Or give him permission to read a particular folder, which includes the template and all the entities it eventually uses.
thanks, i've opened an issue to fix this, subscribe there for updates when the issue is fixed, we are going to check on this thanks for the bug report.
Ok, in this way seems that "\compile\jsreport-3.7.1-405f5Qt-s\chrome" directory is properly moved into tempDirectory specified into AppEnvironment variable.
All I can do now is monitoring the pdf report generation feature on our application, hoping that no unknown process can delete chrome content anymore.
Thanks!
