⚠️ This is a lazy fork of a sourcemapped-stacktrace. To do all things right I need to do a lot of refactoring, for which I do not have time right now. So I did minimal change to be able to use it as npm package. This is a PR with first steps of a refactoring. Highly experimental. Undocumented.
- Support node modules, but check if file is readable
- Support recursive resolution - if source map directs to minified file, than you can pickup sourcemap of minified file
- Implement build script using rollup
const mapStackTrace = default; // puppeteer is not required to use sourcemapped-stacktrace-node// it is used for exampleconst browser = await puppeteer;const page = await browser;page;
ALternatives and usefull links
- online source map tool
- faster source map implementation
- sourcemap decoder
Here goes original readme
This is a simple module for applying source maps to JS stack traces in the browser.
The problem this solves
You have Error.stack() in JS (maybe you're logging a trace, or you're looking at traces in Jasmine or Mocha), and you need to apply a sourcemap so you can understand whats happening because you're using some fancy compiled-to-js thing like coffeescript or traceur. Unfortunately, the browser only applies sourcemaps when the trace is viewed in its console, not to the underlying stack object, so you're out of luck.
Install from npm
npm install sourcemapped-stacktrace
The npm bundle contains dist/sourcemapped-stacktrace.js, if that's what you're after. The built product is not held in this repo.
Include sourcemapped-stacktrace.js into your page using either an AMD module loader or a plain old script include. As an AMD module it exposes the method 'mapStackTrace'. If an AMD loader is not found this function will be set on window.sourceMappedStackTrace.mapStackTrace.
mapStackTrace(stack, done [, opts])
Re-map entries in a stacktrace using sourcemaps if available.
stack: Array of strings from the browser's stack representation.
done: Callback invoked with the transformed stacktrace (an Array of Strings) passed as the first argument
opts: Optional options object containing:
- filter: Function that filters each stacktrace line. It is invoked with (line) and should return truthy/ falsy value. Sources which do not pass the filter won't be processed.
- cacheGlobally: Boolean. If
true, sourcemaps are cached across multiple
mapStackTrace()calls, allowing for better performance if called repeatedly, or when browser's cache is disabled. Defaults to
- Internet Explorer 11 and up
- Microsoft Edge
Several modern browsers support sourcemaps when viewing stack traces from errors in their native console, but as of the time of writing there is no support for applying a sourcemap to the (highly non-standardised) Error.prototype.stack. Error.prototype.stack can be used for logging errors and for displaying errors in test frameworks, and it is not very convenient to have unmapped traces in either of those use cases.
This module fetches all the scripts referenced by the stack trace, determines whether they have an applicable sourcemap, fetches the sourcemap from the server, then uses the Mozilla source-map library to do the mapping. Browsers that support sourcemaps don't offer a standardised sourcemap API, so we have to do all that work ourselves.
The nice part about doing it ourselves is that the library could be extended to work in browsers that don't support sourcemaps, which could be good for logging and debugging problems. Currently, only Chrome and Firefox are supported, but it would be easy to support those formats by ripping off stacktrace.js.
- Doesn't support exception formats of any browser other than Chrome and Firefox
- Only supports JS containing //# sourceMappingURL= declarations (i.e. no support for the SourceMap: HTTP header (yet)
- Some prominent sourcemap generators (including CoffeeScript, Traceur, Babel) don't emit a list of 'names' in the source-map, which means that frames from transpiled code will have (unknown) instead of the original function name. Those generators should support this feature better.