Update:
I got window.JSREPORT_READY_TO_START to work by ckecking "wait for printing trigger", but the measurement are still taken before automatic page breaks.

I have tried both setTimeout and requestAnimationFrame. Is there no way to await chrome-pdf's automatic page breaking before taking measurements?

I need to measure some elements. This works great with the following concept:

1. In a script tag, iterate alle elements and collect element.getBoundingClientRect()
2. stringify the measures and mashal them to the server side via console.log
3. add measurement data to req.data
4. start a second render where I now have access to the measurements

Unfortunately, I'm having trouble with the timing. I'm currently measuring at window.onload. It seems as chrome-pdf applies the automatic page breaks after my measurements. I.e. the boundingboxes will sometimes relate to the position the element had before chrome-pdf added the automatic pagebreaks.

Is there any way to await the complete layout?

I tried with a simple setTimeout but jsReport does not await such timeouts on the client side.
I also tried to set window.JSREPORT_READY_TO_START = false; and then set it to true after my timeout, but jsReport did not wait for this.

Never mind.
I see that the message is truncated at 1000 characters. This is probably reasonable to not bloat the logs.

I solved it by chunking my console.log calls instead.

New problem.
I'm collecting measurement data from my html elements, put them in an array and stringify before sending the data to the server side via console.log. It seems as if the message gets truncated. Is console.log not a reliable way to marshal data to the server?

I get the feeling that the profile pane in jsReport truncates long strings, and the truncated string is also what is what I get in req.context.logs[i].message.

Solved. I got it to work when I changed recipe to chrome-pdf.
Is this as it should, i.e. console.log at the client side only works for chrome-pdf?

I get it to work with your docker run command. But it does not work in my docker-compose environment. What could differ?

My Dockerfile is quite minimalistic. I don't think the prolem is here:

FROM --platform=linux/arm64 jsreport/jsreport:4.7.0

COPY .npmrc /app/.npmrc
ARG NPM_TOKEN

RUN cd /app && npm install \
  handlebars-helpers \
  node-fetch \
  i18next \
  i18next-locize-backend \
  bwip-js \
  @plantrail/ddp

RUN cd /app && npm ls

My jsreport.config.json is quite old. Maybe something deprecated is in here?

{
  "encryption": {
    "secretKey": "secret"
  },
  "logger": {
    "console": { "transport": "console", "level": "debug" }
  },

  "workers": { "numberOfWorkers": 4 },
  "reportTimeout": 600000,
  "httpPort": 5488,
  "allowLocalFilesAccess": true,
  "store": {
    "provider": "fs"
  },
  "blobStorage": {
    "provider": "fs"
  },

  "extensions": {
    "chrome-pdf": {
      "strategy": "chrome-pool",
      "numberOfWorkers": 10
    },
    "express": {
      "inputRequestLimit": "100mb",
      "enabled": true
    },
    "child-templates": {
      "parallelLimit": 20
    },
    "fs-store": {
      "sync": {
        "usePolling": false
      }
    },
  }
}

This is the jsReport section from my docker-compose.yaml. I just added the chrome launch options, but it didn't work:

  jsreport4:
    build:
      context: ../services/jsreport4
      args:
        - NPM_TOKEN
    environment:
      - mode=development
      - chrome_launchOptions_args=--no-sandbox, --disable-dev-shm-usage, --disable-gpu
    expose:
      - '5488'
    ports:
      - '5487:5488'
    volumes:
      - ../services/jsreport4/mounted:/jsreport

The console.log can be seen in the chrome console:

sending req.context.logs to the console at the server in afterRender shows other logs, but not the log from my script tag.

Something is different between my environment (jsreport 4.7 Docker image) and the playground.

When I console.log in a script tag I cannot see this in req.context.logs. I have configured logging to console with level "debug". req.context.logs includes other info and debug logs, but not the one from by script tag.

Do I need to add some extension for this to work?

After upgrading from v4.3 to v4.7 some images on my cover page disappeared.
It took some tinkering to solve this, so I'll post here for others to avoid the same pit fall.

I don't know how many of the requisites has to be true to get into this trouble. My setup:

• the cover page is based on css grid
• images are laid out witout margins, i.e. all the way to the edge of the page
• some images had opacity: 0.3; via css class
• the cover page is prepended via PDF Utils

If I render the cover page separately, all images are rendered. But when the cover page is rendered via PDF Utils and prepended to my report, the images disappear.

After changing opacity: 0.3; to filter: opacity(30%); everything seems to work as it should. I'm happy that it works now but I don't understand why it broke in the first place.

Are you using Handlebars?
I'm not shure what {MREGEFIELD defect} means. Is defect a property of MREGEFIELD? I.e. MREGEFIELD.defect?

I don't think Handlebars has a comparison helper out of the box. #if can only check if a value is truthy.

I'm using the npm package "handlebars-helpers" which for example includes #eq for comparing values, like below. If your use case is a one-off it's probably easier to just write a function. Are you using JSReport Studio? In that case it's really simple to write a comparison helper function in the helper pane and call this function from Handlebars.

Here is how your comparison could look like with #eq.

{{#eq MREGEFIELD.defect "New"}}
    Yes
{{else}}
    No
{{/eq}}

That's really great.
Thank you!

I have had a hard time to debug my scripts. This way I can "forward" my console from the script so I can see them in the profiler. Is this a good solution for this, or is there an easier way to se logs from scripts?