console.log('Application is starting.');
The console.log() method logs a message to the console without providing a line number. Simple but useful.
console.debug('Gets to this point without error.');
The console.debug() method logs a message to Firebug console just like log(), but debug() provides a line number reference.
console.info('DOM is ready, now executing Moo event.');
The console.info() method logs a message to the Firebug console with a blue "information" icon. Line number reference is included.
console.warn('Form field [title] has no value.');
console.warn() sets a warning within the console. The warning provides a yellow background color to easily spot warnings within the console.
console.error('The [title] element is undefined. Bad news.');
The console.error() method places a custom error message within the console with a pink background. Easy to spot.
Each of the above methods accept an "object", or array of objects, and works much like a print-f.
console.log("The %d item has a value of: %d", fifth, myvalue);
This probably looks familiar to a PHP programmer.
Make the most of your Firebug -- send your own message to the console!
Using Firebug’s console() can be quite helpful. Just remember to remove calls to it before going to production as, surprisingly, IE will kick out JS errors aplenty. Or remember to use firebugx.js.
When removing the console calls I do a simple find and replace of
Plus, I know
console.logcan be used the same way in Safari’s developer window.
Thanks for the tips! I know that you can mess with Firebug a little with this:
Thanks for posting. I only knew of
Is there a way to output the “Net” log to a file on my local machine? i.e. I want to output to a file all the URLs of images/swfs/text etc. that get loaded when a page is requested by the user.
@anurag: Good question — I couldn’t find anything.
Ensuring that your
console.xxx()calls don’t throw errors when the code runs outside of a Firebug environment was always a concern of mine. The four options for handling it that I have seen are:
console.xxx()calls before publishing, as noted by the first two commenters above.
Lately, I confess I’ve been doing a combination of (1) and (4). (1) keeps the code as lean as possible, but (4) allows me to miss a few without risking an error.
[ BTW: Dave, I’m new to your blog, but just can’t say enough positive about it. The content, the look, the style. Just right freaking on. You might even have me sold on MooTools, as well. My investment in jQuery on a few projects is probably just at the level where I could conceivably back out and go with MooTools. But that’s a whole different discussion for another time. Anyway, thanks and kudos on the site. ]
If you had a flattr button i flattred you !
There are problems with console logging in different browsers.
Firefox has graete firebug.
But firebug has a lot of functions towork withs CSS. Unuse in Js debagging.
More than oher browsers support firebug.js in different ways.
I wrote short script for basic console.API. It redefine most of console.xxx methods to put logs(warnings,timers,info, group) to
This console work on IE6+, FF, Chrome, Safari, Opera.
Press ‘~’ to show/hide them
in all – IE6+, Chrome, Safari, Opera, FF( still work with FireBug, but done all console. requests).
This may be a silly question but I am liberal arts major and am beginning my venture into the wonderful world of computer science. Where exactly is the logs going inside of the computer’s console. I know that it may not be important to coding but will definitely help me to conceptualize what is going on inside the computer as I write my code.
Similarly, I am compiling a collection of blog posts (www.vaughnruns.com) to help the novice programmer how is beginning with node.js. Do you know of any good books or websites that provide a thorough understanding of the material?