You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: