The Stacktrace section on the Developer tab gives you a look under the hood at how the issue appears within your site's JavaScript. Each stackframe in the Stacktrace represents a JavaScript file where the error appears, and shows you the line of code that triggered the error. The bottom file is where the function call is initiated, and moving up the Stacktrace, you can follow the issue's impact until the final stackframe where the error is thrown.
[developer-overview]
Above the Stacktrace section, you can see the Error Signature and Error Message. Within each stackframe, the problematic line of code is tagged with a red marker and highlighted in blue.
[stacktrace]
You'll also see a Generate Explanation button at the top of the Developer tab for every JavaScript issue. Once you click the button, Noibu will pass that line to the AI system, which generates a human-readable explanation of the problem and its impact. The explanation may also include a Dev Tip–a suggestion to help developers know where to start when investigating the error–and a Solution Inspiration–a code snippet that suggests how the issue might be fixed.
Keep in mind that these solutions are AI generated, and should only be used as a starting point. We encourage you to use the thumbs up/thumbs down buttons to rate each explanation. The more feedback we receive from clients, the more refinements we can make to deliver the best explanations possible.
[js-issue-explanation]
While the Stacktrace speeds up your debugging process significantly, the source of the error may be obscured if the stackframes are pulling up minified code. However, by uploading a Source Map, Noibu can point directly at the source file and line of code that's throwing the error.
While the Stacktrace only serves JavaScript errors, Noibu has a corresponding HTTP Error Details section to help developers debut HTTP errors.
Learn more about the other sections on the Developer tab: Browser & OS Impact, Insights, Last Reproduction Steps, and Top URLs.