@ehmicky@fosstodon.org (@ehmicky) header
@ehmicky@fosstodon.org (@ehmicky) profile picture

Node.js back-end developer. I moved to Mastodon: https://teapawt.org/t.co/m9OLUtOrFC

Remote
Joined October 2012
Photo by @ehmicky@fosstodon.org (@ehmicky)Photo by @ehmicky@fosstodon.org (@ehmicky)Photo by @ehmicky@fosstodon.org (@ehmicky)Photo by @ehmicky@fosstodon.org (@ehmicky)Photo by @ehmicky@fosstodon.org (@ehmicky)
A library for handling JS errors in a simple, stable, consistent way ✍ by @ehmicky 🗂 tagged #javascript #node changelog.com/news/zDVn
1
3
I am migrating from Twitter to #MastodonSocial. Please feel free to follow me there! fosstodon.org/@ehmicky I like their decentralized, open-source, non-profit approach. You should join too!
2
One line in your `.bashrc` (or `.zshrc`, etc.) to use source maps in any Node.js error's stack trace on your local machine: export NODE_OPTIONS="$NODE_OPTIONS --enable-source-maps" #nodejs #node #programming #js #javascript
1
5
9
More information at nodejs.org/api/cli.html#--en… Source maps allow showing the original file/line in errors' stack traces instead of the built file/line when using a build step (TypeScript, Babel, etc.). This comes with a performance cost at load time, so is better used in dev only.
1
1