Published May 12, 2023
Source maps are critical for web development in today’s JavaScript environment.
In fact, all of our build tools—Rollup, Vite, WebPack, ESBuild—transpile and bundle our JavaScript and support source maps out of the box.
Debugging errors in production with transpiled code is nigh impossible. So our tooling creates source maps.
See What are source maps? by Jecelyn Yeen for all of the details.
Private source maps make it harder for an attacker to understand your front-end application.
An attacker can easily use public source maps to view the code in its original, un-transpiled state. The same source maps that make debugging easier make attacking your application easier.
Check out our unobfuscated source code on https://www.highlight.io! It’s readable, public and easy to ingest for developer tools like LaunchDarkly. Our vite bundler generates these source maps with a single flag.
Guess what!
With or without source maps, Chrome Dev Tools makes deconstructing your JavaScript application relatively easy.
For instance, You can open up the Network tab and watch each request and response.
The Application tab also surfaces the data your site is saving locally.
Who cares how the code is written if the results, in both data and network, are readily visible?
Dev Tools will even allow an attacker to reformat the code and use breakpoints to step through it!
And then there’s ChatGPT…
ChatGPT struggles with long code snippets, so it’s not yet a silver bullet for decompilation.
But ChatGPT can de-compile shorter code snippets quite effectively.
Dev Tools will automatically recognize and apply public source maps to your code.
Debugging production issues will be much, much easier, especially if you see errors in your console. With public source maps, Dev Tools can link your errors directly to the de-compiled code. It’s magical.
LaunchDarkly does support private source maps. We even publish a source map uploader on NPM that will send your private source maps directly to our servers.
Our source map uploader works well, but depending on a team’s setup, it can be tricky for users to implement and can become a constant source of bugs due to unique build pipelines and machine types.
However, if you make your source maps public, you don’t have to do any of that work. And you automatically get production source maps for your own debugging in Dev Tools.
It’s a win/win.