node-source-map-support icon indicating copy to clipboard operation
node-source-map-support copied to clipboard

Adds source map support to node.js (for stack traces)

Results 104 node-source-map-support issues
Sort by recently updated
recently updated
newest added

I have noticed that DefinitelyTyped has definitions for source-map-support ; as far as I know their goal is to have them directly in the upstream package, but I haven't found...

enhancement
help wanted

Submitting as a draft to ask if there are any obvious problems with this approach. I also removed the empty line of stderr output to match the behavior of the...

Node 12 added some limited support for async stack traces. I'm impressed that this package supports them, but it removes a useful annotation from them: Given this file: ```js function...

bug
help wanted

I'm submitting this as a draft PR to check if the implementation is acceptable for merging. Fixes #291

Following the link from the readme to https://travis-ci.org/github/evanw/node-source-map-support/builds It looks like the tests have stopped running. Am I looking in the wrong place?

I've got some code, with a stack trace, along with the original file and source map. What can I import and call in order to manually process the stack trace?...

Somethere in code of node-source-map-support there is a check like `(env.SOME_VAR === undefinded)` But in windows there is no global variable `env`, so this code falls out with an error....

I've just encountered the fact that Protractor tests in TypeScript run via ts-node leads to broken stack traces, as both Protractor and ts-node call `require('source-map-support').install()` by default. See [this issue...

Currently, I use **esbuild** to compile code and dynamically transpile and execute user JS using `eval()`, like this: ```js try { if (code) { code = `(function(exports) { ${code} return...