<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Modern JS Tooling Setup for Splunk App / Sourcemaps Not Working Properly in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Modern-JS-Tooling-Setup-for-Splunk-App-Sourcemaps-Not-Working/m-p/542860#M37206</link>
    <description>&lt;P&gt;I'm working on a Splunk app which uses Webpack to bundle and compile the Javascript to ES5. I'm generating sourcemaps using the "source-map" devtool option in the webpack.config.&lt;/P&gt;&lt;P&gt;As detailed in&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Dashboards-Visualizations/Source-maps-for-html-dahsboards-create-react-app/td-p/449022?childToView=807665" target="_self"&gt;this post&lt;/A&gt;&amp;nbsp;by&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/157895"&gt;@aprummer&lt;/a&gt;&amp;nbsp;, Splunk injects some lines of internationalization code during runtime at the top of each page, which throws off the reference points within the sourcemaps.&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/157895"&gt;@aprummer&lt;/a&gt;&amp;nbsp;solved this by regenerating the sourcemaps with a line offset. I tried this approach offsetting the sourcemaps by the 5 lines added at the beginning of each file, and while I did see some success with some breakpoints being hit closer to the entry point of the JS code, they are still not matching up and variables are not resolving properly.&lt;/P&gt;&lt;P&gt;Has anyone else had any success with using Webpack and modern JS tooling within Splunk, and if so, how did you get source maps setup properly?&lt;/P&gt;</description>
    <pubDate>Mon, 08 Mar 2021 16:11:42 GMT</pubDate>
    <dc:creator>jdawsonqmulos</dc:creator>
    <dc:date>2021-03-08T16:11:42Z</dc:date>
    <item>
      <title>Modern JS Tooling Setup for Splunk App / Sourcemaps Not Working Properly</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Modern-JS-Tooling-Setup-for-Splunk-App-Sourcemaps-Not-Working/m-p/542860#M37206</link>
      <description>&lt;P&gt;I'm working on a Splunk app which uses Webpack to bundle and compile the Javascript to ES5. I'm generating sourcemaps using the "source-map" devtool option in the webpack.config.&lt;/P&gt;&lt;P&gt;As detailed in&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Dashboards-Visualizations/Source-maps-for-html-dahsboards-create-react-app/td-p/449022?childToView=807665" target="_self"&gt;this post&lt;/A&gt;&amp;nbsp;by&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/157895"&gt;@aprummer&lt;/a&gt;&amp;nbsp;, Splunk injects some lines of internationalization code during runtime at the top of each page, which throws off the reference points within the sourcemaps.&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/157895"&gt;@aprummer&lt;/a&gt;&amp;nbsp;solved this by regenerating the sourcemaps with a line offset. I tried this approach offsetting the sourcemaps by the 5 lines added at the beginning of each file, and while I did see some success with some breakpoints being hit closer to the entry point of the JS code, they are still not matching up and variables are not resolving properly.&lt;/P&gt;&lt;P&gt;Has anyone else had any success with using Webpack and modern JS tooling within Splunk, and if so, how did you get source maps setup properly?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2021 16:11:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Modern-JS-Tooling-Setup-for-Splunk-App-Sourcemaps-Not-Working/m-p/542860#M37206</guid>
      <dc:creator>jdawsonqmulos</dc:creator>
      <dc:date>2021-03-08T16:11:42Z</dc:date>
    </item>
  </channel>
</rss>

