Debug script in browser's devtools

Answered

Follow

Marc Schluper

October 19, 2018 15:59

(As a newbie) I see people advocate editing JavaScript 

widget.on('processresult', function(sender, ev) { //etc

}

I'd like to debug my code in there, in the browser (F12).

I can see the Sisense code but I cannot find my code.

0

• 

  Moti Granovsky October 22, 2018 15:23

  Hi Marc,

  You can do that by adding the "debugger;" keyword anywhere in your widget or dashboard script, opening the developer console and refreshing. As the script is processed by the browser, it will stop execution at this point in the script and behave just like a manually added breakpoint.

  prism.on("beforemenu", function(){
    debugger;
  });

  0

  Comment actions Permalink
• 

  Bruce Christie February 14, 2019 22:04

  Hey Moti,

  Did you have to change any settings to get this to work?  I added a debugger statement but it seems to be stripped out when transpiling.

   

  Cheers,

  Bruce

  0

  Comment actions Permalink
• 

  Moti Granovsky February 17, 2019 10:48

  Hi Bruce, are you attempting to debug a plugin or a widget/dashboard script?

  0

  Comment actions Permalink
• 

  Bruce Christie February 19, 2019 14:31

  Hi Moti,

  I was attempting to debug a plugin.   The code seems to run fine but it doesn't stop at my debugger statement.

  0

  Comment actions Permalink
• 

  Moti Granovsky February 19, 2019 14:50

  Hi Bruce,

  It should work in plugins without issue. First of all, try placing a "console.log" at the exact location of your "debugger" statement and see if that does work - that is, if that line is really reached. If console.log works but "debugger" doesn't please let me know and we'll look into that. 

  Additionally, with plugins you can use Chrome's DevTools to place breakpoints anywhere in your code. You can find the plugin code in the location outlined in this screenshot below - find the code you're interested in, place a breakpoint and reload to see if that does stop. This is generally a better way to debug plugins than the "debugger" method, which is what I'd recommend only for widget & dashboard scripts.

  

  1

  Comment actions Permalink
• 

  Bruce Christie February 20, 2019 18:18

  Hey Moti - thanks for the response.   Seems that my issue was that entry.json was not set proper;y in my local instance (isProd was true).

  ```

  {
  "isProd": false,
  "watchIgnore": [
  ".hg$",
  ".git$",
  "node_modules"
  ]
  }

  ```

  After that the code was non-minified and I could debug normally.  Thanks.

  0

  Comment actions Permalink

Please sign in to leave a comment.