<![CDATA[wkhtmltopdf versions mismatch in gui and npm]]>command npm view wkhtmltopdf version gives me
0.3.4
while in jsreport GUI it is 0.12.3: 0_1581702618582_Screen Shot 2020-02-14 at 18.15.58.png
Which one does jsreport use?
Because I don't even have 0.12.3
npm view wkhtmltopdf versions outputs:

[ '0.1.0',
'0.1.1',
'0.1.2',
'0.1.3',
'0.1.4',
'0.1.5',
'0.1.6',
'0.2.0',
'0.3.0',
'0.3.1',
'0.3.3',
'0.3.4' ]

]]>https://forum.jsreport.net/topic/1467/wkhtmltopdf-versions-mismatch-in-gui-and-npmRSS for NodeSun, 12 Apr 2026 02:25:55 GMTFri, 14 Feb 2020 17:52:59 GMT60<![CDATA[Reply to wkhtmltopdf versions mismatch in gui and npm on Invalid Date]]>command npm view wkhtmltopdf version gives me
0.3.4
while in jsreport GUI it is 0.12.3: 0_1581702618582_Screen Shot 2020-02-14 at 18.15.58.png
Which one does jsreport use?
Because I don't even have 0.12.3
npm view wkhtmltopdf versions outputs:

[ '0.1.0',
'0.1.1',
'0.1.2',
'0.1.3',
'0.1.4',
'0.1.5',
'0.1.6',
'0.2.0',
'0.3.0',
'0.3.1',
'0.3.3',
'0.3.4' ]

]]>https://forum.jsreport.net/post/6703https://forum.jsreport.net/post/6703Invalid Date<![CDATA[Reply to wkhtmltopdf versions mismatch in gui and npm on Invalid Date]]>The npm package wkhtmltopdf has nothing to do with the jsreport recipe.
It is some kind of wrapper we don't use. Also using the npm view you get back that package version, not the wkhtmltopdf binary version.

The recipe uses by default the binary version 0.12.3 as you see on the screen.

Note there is no reason to use wkhtmltopdf these days unless you maintain already designed reports. Look rather at the chrome-pdf recipe.

]]>https://forum.jsreport.net/post/6706https://forum.jsreport.net/post/6706Invalid Date<![CDATA[Reply to wkhtmltopdf versions mismatch in gui and npm on Invalid Date]]>Yes, I already have got designed reports. Is it feasible to install a particular wkhtmltopdf binary version that can be used by jsreport?If yes, how can I do it?

]]>https://forum.jsreport.net/post/6713https://forum.jsreport.net/post/6713Invalid Date<![CDATA[Reply to wkhtmltopdf versions mismatch in gui and npm on Invalid Date]]>Try to put your wkhtmltopdf to the global path. So you can run it as wkhtmltopdf --version from everywhere.
Then install the recipe again, it should check for presence of global wkhtmltopdf command and use it instead of downloading it.

]]>https://forum.jsreport.net/post/6714https://forum.jsreport.net/post/6714Invalid Date<![CDATA[Reply to wkhtmltopdf versions mismatch in gui and npm on Invalid Date]]>I've installed wkhtmltopdf globally wkhtmltopdf --version wkhtmltopdf 0.12.5 (with patched qt)
But UI still shows me only one possible option of wkhtmltopdf version 0.12.3

]]>https://forum.jsreport.net/post/6725https://forum.jsreport.net/post/6725Invalid Date<![CDATA[Reply to wkhtmltopdf versions mismatch in gui and npm on Invalid Date]]>Unfortunately, this isn't reflected in the ui. You can find path to the used wkhtmltopdf in this file
[app]t\node_modules\wkhtmltopdf-installer\lib\location.js
In the case of global command, you should see just wkhmltopdf there

]]>https://forum.jsreport.net/post/6728https://forum.jsreport.net/post/6728Invalid Date<![CDATA[Reply to wkhtmltopdf versions mismatch in gui and npm on Fri, 21 Feb 2020 04:45:27 GMT]]>I uninstalled all wkhtmltopdf versions locally and then reinstall it by brew cask install wkhtmltopdf and npm install jsreport-wkhtmltopdf
It helped me. Thanks!

]]>https://forum.jsreport.net/post/6732https://forum.jsreport.net/post/6732Fri, 21 Feb 2020 04:45:27 GMT