By Hello, friendly JavaScripters. Do you like knowing what the hell is happening in your production code? If so, I'm sure that's why you use source maps to help you debug your JavaScript exceptions in the browser. Source maps became popular with the proliferation of transpilers like Babel and TypeScript, which allow developers like us to take advantage of new language features while still supporting old, crusty browsers (my favorite).
Right now, you can upload your source maps to Honeybadger, and we'll automatically translate your stack traces when an error occurs—making it much easier to pinpoint the cause of the bug.
We built the original system with browsers in mind, but many of you have been asking if you can also upload source maps for your server-side (Node.js) projects. For instance, you may be writing your API in TypeScript—wouldn't it be great if you could link your stack traces directly to the .ts files in your editor? Of course, now you can. 😄
Node.js projects in Honeybadger can now officially take advantage of source maps, just like Client-Side JavaScript projects can (you can find the language setting under Project Settings -> Edit).
To get started, check out our Using Source Maps guide. How you generate and upload source maps will depend on your tooling and build configuration—two of the most common configurations we see use Webpack and/or TypeScript.
Node's Experimental --source-map-support
Honeybadger also supports Node's experimental --source-map-support flag as of version 14+. If you run node with --source-map-support (and are generating source maps in your build system), your stack traces should be automatically translated before sending them to Honeybadger—you don't even need to upload your source maps in that case!
That's all—head over to the JavaScript exception tracking docs to get started!
