node-source-map-support

On the other hand, their actual dependency list looks closer to this, and this is definitely not comprehensive: https://github.com/ionic-team/capacitor https://github.com/Microsoft/tslib https://github.com/codemirror https://github.com/codemirror/autocomplete https://github.com/codemirror/language https://github.com/marijnh/style-mod https://github.com/marijnh/crelt https://github.com/marijnh/find-cluster-break https://github.com/marijnh/w3c-keyname https://github.com/cure53/DOMPurify https://github.com/electron/electron https://github.com/electron/get https://github.com/debug-js/debug https://github.com/vercel/ms https://github.com/sindresorhus/env-paths https://github.com/sindresorhus/got https://github.com/sindresorhus/is https://github.com/visionmedia/node-progress https://github.com/npm/node-semver https://github.com/malept/sumchecke

Re 1: This is not a problem with TypeScript, but with Node. It's the same with every to-js-transpiled language. You can use https://github.com/evanw/node-source-map-support to get stack traces for your TS sources. Re 2: I do agree that this is a problem but remember that it's all just a community effort. You can always create your own type definitions or enhance existing ones and share on the DefinitelyTyped repository. Also, most of the time if a type definition is out of date or invalid, you can just create your own partial typedef for a module with only those several methods you are actually using. Re 3: IMO it's a feature. By using, for e.g. a bluebird library to wrap third party code in a Promise, you are changing the way how your code is interacting with that library by redeclaring the whole library or some parts of it. TSC is compl

I have some medium/large projects using async-await. There are 2 ways to transpile async-await. a) Default, with regenerator, transpiles it to ES5 b) If your env supports generators (like Node, or newer browsers), you can use async-to-generator plugin. Regenerator gives you unreadable code, but it will run everywhere. async-to-generator gives you (relatively) readable code. Source maps support has improved a lot, and you can choose to see only your original code while debugging. You'd be setting breakpoints on your code instead of transpiled code. So you should be fine whether you're using regenerator or async-to-generator. There might be corner cases (very rare) depending on your env; in which case if you're using regenerator you might need to switch to async-to-generator to find the bug. Source maps work well with node-inspector. If you

So is there a way to use the source maps with node.js stacktraces? Specifically, I tried this test.coffee: throw new Error("Test") Now running it with coffee test.coffee still reports the wrong line number in the stack trace. There's supposedly node-source-map-support (https://github.com/evanw/node-source-map-support), but even installing that and adding "require 'source-map-support'" won't help.