The latest version constantly logs output in to the chrome developer console
The latest version constantly logs output in to the chrome developer console. It should never print anything in to the chrome console unless explicitly in development mode. For web developers it's just filling up the console with messages on every single site. This needs to be turned off now.
Fixed in version 8.2.7
-
Kumar Anirudha commented
A quick fix is to edit the config of wikiwand extension and allow it to run only on wikipedia or related sites.
*://wikipedia.org/* -
Anonymous commented
This is NOT FIXED and has REGRESSED AGAIN. This issue needs to be made OPEN again. See the issue re-raised here: https://wikiwand.uservoice.com/forums/247843-wikiwand-website-extensions/suggestions/37183561--do-not-show-on-websites-keeps-getting-logged-in
Seconding what Danilo says - this has been going on for THREE YEARS. Just fix it!
-
Nathan West commented
If you use webpack or uglifyjs in your build process, there's a way to configure it to remove logging statements in production builds
-
Kerry commented
Just realized I can right-click on console messages and choose to hide them from certain sources, like this one. Solved my gripe :)
Keep up the good work, Wikiwand makes me love wikipedia even more
-
Guillaume Danguin commented
Guys. Use logpoints.
It's a new feature in Chrome and Firefox is working on it too.
It logs things. It doesn't add the logs to the prod build.
Use that. -
deedee commented
Please fix it. It is a big problem fpr developers!
-
Ayush Sachdeva commented
The chrome extension prints "do not show on websites" on websites whenever I click anywhere on any page. Please remove this log. This is a huge annoyance for developers and needs to be prioritised.
-
Naud commented
Can't you have a separate version of Wikiwand with debugging on while users have no debugging? For example a debug variable that's false for users, but true for developers, so you don't need to remove all logging code from the extension every time you publish it. The only thing you need to do before publishing is changing that one value from true to false.
-
Anonymous commented
You should have a build script that either builds for production or development. And in production mode all the console.logs should be removed.
-
Anonymous commented
A quick workaround for example can be something like adding a line with:
console.log = function(){};
to the beginning of the javascript file, and just comment it while developing. -
Nicolas De Smyter commented
Maybe you could just add an option or a settings page to the plugin. So you can set that option to "debug" for your sake, and "default" for everbody who doesn't care for your debug logs (like... everybody!)
Now I have to disable the plugin just because of these annoying logs. I am a developer, so use the console constantly.
-
Anonymous commented
This issue is still occuring. There are absolutely insane amounts of logging occurring while I am developing other applications. Please turn this off immediately for god's sake. It should be a quick configuration change.
-
Josh commented
If, like me, the only feature you need is automatically redirecting Wikipedia links to Wikiwand, you can uninstall this extension and replace it with ZeroWiki: https://chrome.google.com/webstore/detail/zerowiki/cklaghejbnabhfdlaelhbjdepkfodkcj. Just make sure you pick "Wikiwand" as the mirror after installing.
(Not only does ZeroWiki keep your console quiet; it also keeps its permissions confined to "Read and change your data on all wikipedia.org sites", rather than demanding "Read and change all your data on the websites you visit" like Wikiwand.)
-
Alejandro commented
Please remove this logging. As already stated in other comments, you can use a combination of the debug npm package, conditionally enabling it with some localStorage key and/or multiple dev/prod builds.
-
Anonymous commented
This is super annoying. Don't spam my console. Especially when I've disabled your unnecessary "feature"
-
Anonymous commented
Maybe use `debug`, from npm? Some kind of localStorage key, or global variable, which toggles the noisy logging, would probably work fine.
Partial fix, for any developers frustrated with this right now:
In the DevTools console, under settings, you can restrict console output to "selected context only"--this silences the logging from wikiwand, but also from any other js contexts.
-
[Deleted User] commented
+1. Came here to report this. I don't mind the logging, but it shouldn't be running on all websites when I have quick-definition turned off!
-
Anonymous commented
Indeed it always show "do not show on websites" from jquery. Thanks for your work!
-
developer commented
+1 please
-
Anonymous commented
+1 to this, all the console logs are clogging up my own debugging on chrome projects. The webpack suggestion in an anonymous comment below is a good one that I've used.