All Apps and Add-ons

When debugging a Splunk App's JavaScript in VSCode the breakpoints are moved forwards by several lines

John235711
Engager

I'm using VS Code and the "Debugger for Chrome" plugin to debug my Splunk App's Javascript code. Whenever I start a debug session the red dots that represent the breakpoints are moved several lines forwards. Using Chrome DevTools it appears that the following two lines are being injected by Splunk at the beginning of my JavaScript file:

// Translations for en_GB
i18n_register({"plural": function(n) { return n == 1 ? 0 : 1; }, "catalog": {}});

I believe that this is the reason for the breakpoints changing their location.

Is there a way to stop Splunk from injecting these two lines? If not, is there any known workaround for VS Code or other Javascript debugging tools?

Tags (1)

aprummer
Explorer
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...