Console.log always returns undefined in Chrome

Question

I just encountered this weird problem. I don't remember I have it before but it has been quite a while since last time I develop any Chrome stuff.

The picture below pretty much speaks it by itself:

Why does Chrome console constantly return undefined for console.log command? Any console.log used in js scripts also return the same.

Update

console.log.toString() returns "function log() { [native code] }"

because console.log does not return anything! That means it returns undefined. — epascarello, Oct 15 '18 at 12:55
@epascarello why are you so impatient? can't you look at the screenshot and see the real problem? — Nurbol Alpysbayev, Oct 15 '18 at 12:58
@NurbolAlpysbayev Explain how it is a dupe? `var a = 1;` produces undefined without the console line. — epascarello, Oct 15 '18 at 12:59
@epascarello the author incorrectly wrote "returned undefined" because of poor knowledge of english but if you look at the screenshot, you can see `console.log` *prints* incorrectly — Nurbol Alpysbayev, Oct 15 '18 at 13:01
Actually it never prints anything. Maybe some non-standard environment. — Nurbol Alpysbayev, Oct 15 '18 at 13:04
My guess, something overwritten console.log(), but impossible to tell with what is provided. What does `console.log.toString()` return? My guess it is not `"function log() { [native code] }"` or you filtering out logs. — epascarello, Oct 15 '18 at 13:06
@epascarello, indeed, I should have used the word `prints` and it turns out it's a duplication of the question you linked. — Anthony, Oct 15 '18 at 13:14

score 27 · Accepted Answer · answered Oct 15 '18 at 13:07

27

Are you filtering the messages by chance? Look in the upper right corner of the console to see if it says “1 hidden”.

Screenshot of devtools, "Hide all / 6 hidden" emphasized

answered Oct 15 '18 at 13:07

Josh Lee

1 Answers1