Vue plugin prevents logging of errors to the console
See original GitHub issueDo you want to request a feature or report a bug?
A bug
What is the current behavior?
When Raven Vue plugin used, Vue will stop to log errors encountered during components rendering to the console
What is the expected behavior?
Expected Vue to log errors.
Raven version: 3.26.3 OS: Windows 10 Used via JSPM
This most likely happens because Raven.js defines Vue errorHandler
, but starting from Vue 2.2.0 when it’s not undefined
, Vue won’t log errors to the console. See errorHandler
docs.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:10
- Comments:17 (6 by maintainers)
Top Results From Across the Web
Error handling, debugging, and tracing in Vue.js
In this tutorial, we'll demonstrate how to handle errors, set up a debugger, and trace errors efficiently in Vue.js.
Read more >How enable console log in VUE-CLI during development
Now, if you want console.log stripped from production build ... TerserPlugin = require('terser-webpack-plugin') const isProd = process.env.
Read more >vue-logger-plugin - npm
Specify an appropriate level to limit the amount of information logged. For example, using the 'warn' level will log the 'log', 'error', and...
Read more >Handling Errors in Vue.js - Raymond Camden
A look at handling errors in your VueJS applications.
Read more >API Reference | Vuex
An array of plugin functions to be applied to the store. ... unsubscribe = store.subscribe((mutation, state) => { console.log(mutation.type) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Agreed. This side-effect of integrating vue in sentry should really be documented… Personally spent a lot of time and frustration because of this.
Agreed -for users that is. however, suppressing errors for developers really just makes this whole thing super ironic. (Install sentry to catch issues you cannot see yourself on the clients; Ends up suppressing more issues)
I don’t agree with the sentiment that JavaScript console errors should be suppressed for end users.
When you’re casually browsing the internet and something doesn’t work, say you click on something and expect something to happen but it doesn’t, or you’ve placed an order and the success page takes longer than expected, how many of you developers check the JavaScript console? Im surprised if that’s not at least most web developers. It’s ironic that were the ones wanting to suppress errors for end users. It’s almost like killing logging for client side systems, sure probably the client will never look at the logs, but conceptually they should still exist on the client side.
Unless you are super paranoid about the inner workings of your app for whatever reason, I really don’t understand the necessity for changing the default behaviour of JavaScript.