Skip to content

Commit 52ec520

Browse files
priscilawebdevLuca Forstner
andauthored
Update docs/platforms/javascript/common/sourcemaps/troubleshooting_js/debug-ids/index.mdx
Co-authored-by: Luca Forstner <[email protected]>
1 parent 0ef287f commit 52ec520

File tree

1 file changed

+1
-1
lines changed
  • docs/platforms/javascript/common/sourcemaps/troubleshooting_js/debug-ids

1 file changed

+1
-1
lines changed

docs/platforms/javascript/common/sourcemaps/troubleshooting_js/debug-ids/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This documentation provides an in-depth look at Debug IDs, explaining how they w
99

1010
Modern web applications often use some kind of build process when using JavaScript. This build process takes some input JavaScript, transforms it in some way, then outputs JavaScript that is served alongside the website. Some example transformations include minifying JavaScript code (so the final JavaScript bundle is smaller and faster to load) or removing TypeScript types (only JavaScript can run on the browser).
1111

12-
As a result, the JavaScript code running in production is typically not the same as the code written by the developer in the source editor. Instead, it has undergone several transformations, such as [minification](https://developer.mozilla.org/en-US/docs/Glossary/Minification), [transpilation](https://www.typescriptlang.org/), [downcompilation](https://babeljs.io/), [transformation](https://rollupjs.org/), [polyfilling](https://developer.mozilla.org/en-US/docs/Glossary/Polyfill), and others, aimed at improving performance and ensuring cross-browser compatibility.
12+
As a result, the JavaScript code running in production is typically not the same as the code written by the developer in the source editor. Instead, it has undergone several transformations, such as minification, transpilation, downcompilation, bundling, polyfilling, and others, aimed at improving performance and ensuring cross-browser compatibility. Some common tools that transform code in such ways are Babel, Vite, Webpack, Rollup, Terser or swc - which are often used by higher level tools like Next.js, Nuxt, Create React App and similar.
1313

1414
Stack traces are essential to debug errors, but stack traces that come from generated JavaScript are often unreadable or unusable! They look nothing like the code you wrote, you can’t connect them to your source code repository, and minified variables or function names make you lose context about what is happening.
1515

0 commit comments

Comments
 (0)