Root causing javascript issues with stack trace information

Finding the root cause of a javascript error on your website can be quite challenging. Especially if you minify your files, but even without having minified files understanding what caused your code to fail can be quite cumbersome. In this document we go over how to get the most out of stack trace information to understand the cause of your javascript errors.

 

Steps to find the root cause of a javascript error in a file

  1. Get access to the minified file via the stack trace in the Noibu platform.
    Screen_Shot_2021-02-16_at_4.34.50_PM.png
  2. Copy the file name and paste it in a new browser tab
file.png

    3. Go to https://chrome.google.com/webstore/detail/javascript-and-css-code-b/iiglodndmmefofehaibmaignglbpdald?hl=en  in a new tab and download the extension for your chrome browser.

 

     4. Go back to Noibu and copy the function name in blue, in the picture below its “onscroll”

    • In some cases the "At" field will not be helpful. In those cases use the "Javascript Error Message" text to try to extract a keyword. In the case of the image below we would use the "prevArrow" text.
    • Screen_Shot_2021-02-16_at_4.38.07_PM.png
Screen_Shot_2021-02-16_at_4.37.20_PM.png

 

     5. Go back to the tab where you opened the file that is throwing an error

 

            1. Press "Beautify Now"

Screen_Shot_2020-12-14_at_12.10.48_PM.png

            2. Press cmd+f if youre on mac or ctrl+f if you’re on windows in the result window to search      

                 the  whole page

            3. Paste the copied function name from step

            4. This should give you the function that failed

            5. Use the details found in this function to search your non-minified files for the root                                     cause.  In this above example you would use the pointerDownScroll  function name to                             pin-point the exact location of the error in your non-minified file.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.