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'm having an issue with the RegExp at [source-map-support.js#L113-L114](https://github.com/evanw/node-source-map-support/blob/master/source-map-support.js#L113-L114) matching it's own comment above. Can you change the comment so that it doesn't?

This one might be a little more contentious, but this adds filtering to the stack frames for common runtime libraries. Effectively adds blackboxing to the stack traces.

`require('source-map-support').removeFromCache('path/to/foo.js')` will remove `path/to/foo.js` from the source map cache. ## Motivation I use am using `babel-register`. At some point, my program notices that a file changes. So it calls ```...

I'm inserting multiple lines at the top of a Webpack bundle for the sake of making this work when I load the bundle in Meteor, like so: ``` js require("source-map-support/register");...

When using node-source-map-support (v0.2.10) via `babel-node`, file paths are being lost for the files local to the package. This also occurs when I override babel's copy to `[email protected]` With the...

Related to #100. On NodeJS, as far as I can see, base64 source maps work nicely. However, the paths inside the stacktraces are relative to the compiled file, where I'd...

Does node-source-map-support support inline sourcemaps encoded into data url's? I'm writing ansible modules in javascript using webpack to package the javascript together into a standalone file. Ansible module's can be...

Having a problem using `source-map-support` in a Chrome extension. Narrowed it down to a failed attempt to retrieve an extension-specific page (`extensions::uncaught_exception_handler`) via XMLHttpRequest. The impact is that any errors...

Hi! I'm working on https://github.com/mozilla/tofino and we have some interesting requirements. It appears that we need absolute `file://` paths in our `sourceMappingURL` to support source maps in the (Chrome) devtools...

help wanted

Thanks to https://github.com/evanw/node-source-map-support/pull/79 this supports Electron already (an environment where we are both in a "browser" and in "node"). It might be good to do the same logic here, so...