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!

[Puzzles] Solve, Learn, Reuse: Word-play

This puzzle series (first published here) is based on analysing words.Some of the statements in your puzzle ...

Tuning Edge Processor in Hybrid Mode: What Limits Each Data Path

When you run Edge Processor in hybrid mode, alongside a Splunk heavy forwarder on the same host, two questions ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...