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?
I think we have the same problem. I fixed it by injecting 6 lines to my source-map: https://answers.splunk.com/answers/765360/source-maps-for-html-dahsboards-create-react-app.html?chil... and https://gist.github.com/prumand/73ae1a01d22029d7969ce8a5dcaa453d