It appears that if the "Chrome" object is defined for a recipe, it also needs a viewport Width / Height. I am unclear how this object got set to begin width as I am almost exclusively using the editor.

Generates Error:

chrome": {

        "printBackground": true

    },

Does not generate error / Works:

"chrome": {

        "printBackground": true,

        "viewportHeight": 1024,

        "viewportWidth": 1024

    },

Not a pressing issue as this works for what I am doing. Might be nice to have a default width / height if not specified.

When I attempt to specify PDF meta data in the edtor, I am getting an Error: Error when trynig to update "templates" collection. Input contain values that does not match the schema. schema-valdation errors: chrome vewportHeight should be number, null.

This does not appear to happen in the JSReport playground. I also can specify template data by directly editing the recipe using VSCode. That said, I would like to be able to do this with the editor. JSReports v 3.9, recipe: chrome-pdf, engine: handlebars

Any thoughts on why this is happening would be greatly appreciated.

Figured this out. In case anyone else cares, you can click "profile" on the report and see the console.log output.

I would like to use console.log inside JSReport Studio and have it output to the browser console or some place in Report Studio that is accessible to the report creator. My understanding is that the Debug extension used to do this. When I attempt to install this extension, it indicates that it is not compatible with the "Core" extension.

I am aware that debug statements are displayed in the node.js window but I would like to be able to show these messages to the report writer who may not be a developer or have access to the node server console. Thanks.