I've used setInterval() plenty of times in typical scripts, but not with userscripts. For some reason, console.log() isn't working, but only inside of the setInterval. The alert, however, is working. Any ideas..? Should I not be using console.log?

To clarify, the first console.log("Started!"); does in fact print started.

(function() {
    console.log("Started!");
    setInterval(function(){ findAndReplace();}, 3000);
})();

function findAndReplace() {
    alert("hi");
    console.log("Hey");
} 

I've used setInterval() plenty of times in typical scripts, but not with userscripts. For some reason, console.log() isn't working, but only inside of the setInterval. The alert, however, is working. Any ideas..? Should I not be using console.log?

To clarify, the first console.log("Started!"); does in fact print started.

(function() {
    console.log("Started!");
    setInterval(function(){ findAndReplace();}, 3000);
})();

function findAndReplace() {
    alert("hi");
    console.log("Hey");
} 

• javascript
• setinterval
• tampermonkey

• Hmm.. seems to work here: jsfiddle.net/seyenaz/ss20m0qt – Omri Aharon Commented Mar 7, 2015 at 17:33
• It works in IE, but not FireFox. – Steve Wellens Commented Mar 7, 2015 at 17:38
• 1 This works perfectly fine in Tampermonkey. Something you are not showing us is the problem. Complete (but concise to the problem) script? This includes the metadata block. Chrome and TM versions? Non-standard TM settings? – Brock Adams Commented Mar 7, 2015 at 21:16
• 3 Also be aware that some few web sites do trash the console functions; I've seen this on about 3 sites, IIRC. The console.log("Started!") would be firing (just) before that happens, if that is your case. – Brock Adams Commented Mar 7, 2015 at 21:21
• 3 @BrockAdams this was correct, Twitter overrides this. I ended up just putting console.log = console.__proto__.log at the start of my functions and it works just fine now. – Christopher Wirt Commented Mar 7, 2015 at 22:00

3 Answers 3

The answer supplied by OPer didn't work for me, it seems that's no longer an option. Grant GM_log to your script and use the GM_log function as a substitute for console.log.

Add this to the userscript header:

// @grant GM_log

Use this in your code:

GM_log('<my debug message>');

Apparently, Twitter overrides console.log. The "solution" is to put console.log = console.__proto__.log at the top of my functions.

To your tamermonkey script header add

// @grant GM_log

then console.log("hello world"); should work