Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sourcemap links and github integration #87

Open
urbanautomaton opened this issue Oct 24, 2014 · 0 comments
Open

Sourcemap links and github integration #87

urbanautomaton opened this issue Oct 24, 2014 · 0 comments
Labels
feature request Request for a new feature

Comments

@urbanautomaton
Copy link

Hi,

We're now using the JS reporter in production, and it's been really helpful already - thanks very much. The only issue we have is with the links from the error view to our application repo.

Our sourcemaps point to unminified locations available via our site, so for example the sourcemap for /assets/js/main.min.js points to locations in /javascripts/app/main.js - this needs to be the case so browser dev tools can fetch the original source.

In bugsnag's error view, these links point to our github repo. There, though, the files referred to are all contained in a public/ directory, so the github links don't work.

Would it be possible for the JS reporter to include an option for specifying the location of static assets within our repo?

Regards,
Simon

@snmaynard snmaynard added the feature request Request for a new feature label May 16, 2016
kattrali pushed a commit that referenced this issue Apr 22, 2021
Add integration test for cancelling breadcrumbs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for a new feature
Projects
None yet
Development

No branches or pull requests

2 participants