Resolving sourcemaps

[XBDRX]

Hi

I'm using Gulp+Webpack+React. I've added stacktrace.js to the mix but the exception files and line numbers are always reported in the bundles rather than the original files.

I've previously used stacktrace (stable build) with Gulp+Webpack+Angular without problem so am I just doing something wrong?

[eriwen]

I'm going to assume that you're using the version of stacktrace.js that is on the master branch (basically 1.0 beta) which supports sourcemaps.

We got a question similar to this a few months back. They provided an example repo.

Depending on the reason sourcemaps aren't resolved, there may be useful information in the Promise errback function. This change fixed the other issue.

If the example repo doesn't help you fix your problem, could you please provide more detail or an example so we can help you further?

[auchenberg]

Using https://github.com/mbrgm/stacktrace-js-sourcemaps-example/pull/1/files, I'm seeing some wrong request made by stacktrace.js where the webpack:// protocol prefixes are included, which for obvious reasons makes the requests fail.

From Chrome DevTools console:

Are these prefixes not supported, or is it a bug within stacktrace-gps?

[eriwen]

This should be working correctly since stacktracejs/stacktrace-gps#18 has been merged and pushed.

Would be awesome if someone other than I can confirm that.

[eriwen]

@gbaumgart The best way to do that is to enable offline mode. All stacktrace.js methods accept {offline: true} which prevents all network requests. In the future, we may give an option to specifically disable source maps.

[eriwen]

I believe the OP's request was fulfilled here. Please open a new issue if there is anything unaddressed here.