1

For my VUE JS ( VUE CLI) application, I have uploaded a source map to Bugsnag using webpack-bugsnag-plugins. But I am wondering if there is any way that the source map is not shown in the browser. I tried deleting the created *.map files after uploading to bugsnag in the post-build script, but then the error event is not mapped to the source file in Bugsnag.

I am worried about exposing my source code in the browser with productionSourceMap = true, but I wanted to have the full trace of my error in Bugsnag.

Can anyone help me with this?

Improve this question
2
  • This was successful! After sometime Bugsnag started to show full stack trace correctly. Commented May 25, 2021 at 14:10
  • 1
    would be great if you could add your own answer with some of the details. Having a Laravel Vue application and would love to see how you set things up. Commented Nov 17, 2021 at 0:25
Related questions
23
VueJS Stack Traces Do Not Show Where Errors Occur
5
How to use BugSnag inside of a nuxt.js app?
5
Webpack source maps for some .vue (and .ts) files no longer contain original code (sourcesContent)
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.