npm install @jsreport/jsreport-wkhtmltopdf
This recipe is using wkhtmltopdf to transform html into pdf. Wkhtmltopdf includes more advanced pdf features like clickable links, table of contents or outlines(bookmarks).
Options reflects the wkhtmltopdf options. See its docs for details. Currently supported options are:
You can globally wkhtmltopdf recipe to add wkhtmltopdf supported options this way:
"extensions": {
"wkhtmltopdf": {
"proxy": "url",
"any other option supported by wkhtmltopdf": true || "value",
//options like env variables passed to wkhtmltopdf child process
"execOptions": { ... }
}
}
See the list of supported options here.
The header and footer parameter requires full html. For example
<!DOCTYPE html>
<html>
<body>
Header...
</body>
</html>
See the header with page number demo in the playground.
Accessing local files through wkhtmltopdf is disabled by default. You can enable it using this config:
"extensions": {
"wkhtmltopdf": {
"allowLocalFilesAccess": true
}
}
Unfortunately wkhtmltopdf will produce different sizes of pdf elements when rendered on Windows vs Unix platform. We recommend to design your reports on the same OS where you plan to run your production jsreport instance because of this. If this is not an option for you, you may try to use the wkhtmltopdf's zoom property with an approximate value of 0.78125 to match windows size in linux/macOS machines, but you probably will need to update also the margin property too because it seems that in some cases changing the zoom has an impact in the margin.
Another option is to apply the following css in your template to adapt the sizes on your local or production templates.
body {
transform-origin: 0 0;
-webkit-transform-origin: 0 0;
transform: scale(0.654545);
-webkit-transform: scale(0.654545);
}
Rendering request template can include wkhtmltopdf property with specific options.
{
template: {
wkhtmltopdf: {
orientation: "landscape"
}
}
}