I remember the day I learned that I could use console.log to test my app instead of having to alert everything. Man did I feel good and smart. Everything was very smooth, and fast. No longer did I have to close every single alert in order to get to the next one, nor did I had to worry about leaving some rouge alert saying You made it into the if!
But then again every time I tried to test in IE beauty became the beast. Instead of getting a good log in the IE console which… ooops doesnt exist, I got a nasty js error saing what the hell is console.log ?
So I got into the habit of cleaning up my console.logs after using them which really didn’t help me testing out something in staging or dev because when you are making heavy client side apps, everything is ajax based, and you always need to know if you are showing the exact data that you received or if your js code is doing something funky.
Solution simply use another function that checks if console.log exists and if so log it, else don’t
function cLog( text ){
if( (window['console'] !== undefined) ){
console.log( text );
}
}
Updated with a better solution
if(!this.console){
window.console={
log:function(){}
};
}
— Update as of sep 28 2014,
Using a grunt task to remove all your logs helps prevent deployment of logs, and avoid IE9 errors.
https://www.npmjs.org/package/grunt-remove-logging
Enjoy!
Digital Caveman 
Would it work in IE to use a div as a fake console log?
function cLog( text ){
if( (window[‘console’] !== undefined) ){
console.log( text );
} else {
$(‘#console_log’).append(text + ”)
}
}
Great idea Alex!
I guess you could put and absolute positioned element at the bottom of the screen to simulate as much as possible a typical console.log
Then all you have to do is remove it from the DOM once you are finished. jQuery shouldn’t fire an error if the DOM element does not exist I believe.
Or if we are already removing the div might as well remove the DOM console.log to I guess. But yeah this should work.
You know you’ve made it what your solutions pop up when i google search errors. Nice work huevos
Hey keith! thanks for the good vibes =)
Works Beautifully! Just read this post, in middle of a project, and was facing this problem.
Hey Rupin! Nice to hear from you man. Glad it helped you out. Hope things go great with your project.
I like the helpful information you provide in your articles.
I’ll bookmark your weblog and check again here frequently.
I’m quite sure I’ll learn a lot of new stuff right here!
Good luck for the next!
Good article. I’m dealing with many of these issues as well..
When someone writes an piece of writing he/she keeps the thought of a user
in his/her brain that how a user can be aware of it. So that’s why this article
is perfect. Thanks!
Hi mates, good piece of writing and pleasant arguments commented here,
I am truly enjoying by these.
Hurrah, that’s what I was looking for, what a stuff!
existing here at this webpage, thanks admin of this
site.
whoah this blog is excellent i like reading your posts.
Stay up the great work! You already know, many persons are huntung round for this
information, you can help them greatly.
I hardly drop comments, but i did some searching and wwound up here
Forget console.log | Digital Caveman. And I actually do have a few
questions for you if you do not mind. Could it be just me or does it look like some of the comments look like they are
written by brain dead people? 😛 And, if you are posting att other online
sites, I’d like to keep up with everything new you have
to post. Would you make a liszt of every one of your communal sites like
your twitter feed, Facebook page or linkedin profile?
http://about.me/oscarvillarreal