using node inspect flag causes jsreport to freak out

  • When I try to start my app with node --inspect flags, jsreport freaks out. here's what it looks like:

    Debugger listening on ws://
    For help see
    Debugger attached.
    2018-08-29T16:02:32.018Z - info: Initializing jsreport@2.2.0 in development mode using configuration file: none
    2018-08-29T16:02:32.019Z - info: Searching for available extensions in /Users/ksefchik/dev/trafficware/pod-central/podlink/pm2-jsreport/jsreport/
    2018-08-29T16:02:32.030Z - info: Extensions location cache contains up to date information, skipping crawling in /Users/ksefchik/dev/trafficware/pod-central/podlink/pm2-jsreport/jsreport/
    2018-08-29T16:02:32.036Z - info: Found 31 extensions
    2018-08-29T16:02:32.063Z - debug: Writing extension locations cache to /var/folders/bh/144vlxjx32vblw1zt_1lp1yw0000gn/T/jsreport/core/locations.json
    2018-08-29T16:02:32.064Z - debug: Discovered 31 extensions
    Starting inspector on failed: address already in use
    Waiting for the debugger to disconnect...

    Here you can see I launch the process with the --inspect-brk= flag. Then, for some unknown reason, the inspector appears to try to start again, which crashes the app.

  • Hm, it works for me in vscode, the output looks like this.
    Just a note, I guess it don't help you.

    C:\Program Files\nodejs\node.exe --inspect-brk=18548 server.js 
    Debugger listening on ws://
    2018-08-29T21:11:27.377Z - debug: Writing extension locations cache to C:\Users\janbl\AppData\Local\Temp\jsreport\core\locations.json
    2018-08-29T21:11:27.378Z - debug: Discovered 31 extensions
    2018-08-29T21:11:28.036Z - debug: Extension authentication was disabled
    2018-08-29T21:11:29.045Z - debug: Extension fs-store was disabled
    2018-08-29T21:11:29.052Z - debug: Extension authorization was disabled
    2018-08-29T21:11:30.126Z - debug: Creating samples is disabled
    2018-08-29T21:11:30.147Z - debug: Extension public-templates was disabled

    node 8.11.3

  • administrators

    hi! i made some comments here why using --inspect in this way will not work for jsreport, in the link you will find two solutions if you want to debug jsreport process. these days i just use ndb which handles the debugging workflow smoothly no matter if there is just single process or multiple processes in app. just FYI, in case it helps you.

Log in to reply

Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.