The JavaScript the execution environment is running, be that the browser for client-side applications or Node.js for server-side applications is not always the same code we write. Sourcemaps are used in JavaScript & other languages / technologies, but JavaScript is where we seem to use them the most. NET applications in debug mode), these are similar. Why should you care about these things called sourcemaps? If you’re familiar with debugging symbols (the *.pdb files you get when building. Style debugging in VSCode, but also attaching to a running process on my laptop as well as attaching to the Node.js process running within a local Docker container.ĭeveloper & Chief Course Artisan, Voitanos LLC. I found the available explanations I came across lacking in helping bridge the gap I needed to make sure a build process would support no only Next, I’ll explain the part that I found challenging: understanding how VSCode deals with sourcemaps. I’ll go into more depth explaining how they work for those interested. You need to understand what sourcemaps are and why you should care about them. In this post I’ll explain how it works, the guts of JavaScript sourcemaps & how to take control over them to get debugging to work in VSCode. The how this works part isn’t covered well in my opinion… once I understood this, it was easier to set it up.

I found it challenging to get it working with Node.js applications written in TypeScript. How to configure the editor to debug Node.js applicationsĪs well as how to debug applications that are written in TypeScript and transpiled to JavaScript.

Visual studio code debug gulp tasks