This workshop is important because:

finding your errors and fixing them will make you a better developer. The chrome developer tools are designed specifically to help you look carefully through all aspects of your webpage in order to gather information about how it is working. They are an indispensable resource that you should quickly get familiar with.

After this workshop, developers will be able to:

• use the console tab to gather diagnostic information about their code (read various error messages and logs of their own creation).
• use the sources tab to view the JavaScript on the page.
• use the elements tab to view an manipulate the DOM and styling.
• view their sites in mobile mode with the device mode.

Before this workshop, developers should already be able to:

• open the developer tools using right click and "inspect element" or using the keyboard shortcut option+cmd+i.
• use console.log() to output useful information from their JavaScript files.

The Chrome Dev tools documentation has recently been updated and improved.

The console is where you see the output from your program. If things are running smoothly, you'll see a bunch of console.log messages of your own creation that give you information about the status of the code. You can use these to print values that will give you an idea of whether the values are as expected!

When things aren't going well, you'll have a number of red errors to read, interpret and correct. We'll cover both below.

Tips for console logging:

• Write descriptive log messages.

   // WORSE
   console.log("test");
   // BETTER
   console.log("inside add button click event - this is ", this);

• Don't reuse the same log message in multiple places; it will be hard to tell where messages came from once we get out of the chrome dev tools.

• When adding an object to a string log message, use console.log's ability to take multiple comma-separated arguments. When you give console a string and object/array concatenated (with a +), the object/array is converted to a string (poorly, in most cases). When given as a separate value, indicated by adding a comma, the system will print out objects and arrays much more completely.

   var animals = {a:"aardvark", b:"baboon"};
  
   // WORSE
   console.log("animals is " + animals);
   // logs "animals is [object Object]"
  
   // BETTER
   console.log("animals is ", animals);
   // logs "animals is  { a: 'aardvark', b: 'baboon' }"

Read error messages! Sometimes error messages are awesome. Sometimes not so much. Be aware that in the chrome dev tools console, the right hand side of an error line often shows you the file name and line number that the error came from.

The error source above was the demoFunctions file, line 10.

This is extremely useful for finding errors and eliminating them!

This blog post explores a few of the most common errors that you will see display in the console. Here are just a few:

This error means that there is a symbol that is unexpected somewhere in the code. Sometimes that means that you have an extra } as is indicated above. Sometimes it means you're missing a closed bracket or a closed parentheses. In that case, it will tell you that the next symbol it can't properly understand, which can look a little cryptic:

Simply look at the line indicated and move backwards to see if there are any unclosed brackets or parentheses nearby.

This means that you haven't declared a variable before attempting to use it. Make sure that you look through the code at where variableName is defined and used. Ensure that you declare it at a scope that is accessible to the place where you later attempt to use it.

This means that you have attempted to run a function on variable a which is a number, string, array, or any other data type (but not a function).

This usually means you've used = instead of === for comparison! In the example below, it should say if(combineWords() === word)

debugger is a JavaScript tool for debugging! It lets you pause your code on a specific line, wherever you write the keyword debugger. While it's paused, you can examine the scope, the call stack, and other useful information. Across many languages and tools, interactive pauses like this are called "breakpoints".

Chrome's "Sources" tab provides a nice Graphical User Interface, or GUI (pronounced "gooey") for the debugger tool.

Here's an example you can use to explore recursion with debugger:

	function count(n){
	    console.log('counting down...');
	    console.log(n);
	    debugger;
	    if (n > 0) {
	        count(n-1);
	    } else {
	        console.log('at the bottom!');
	    }
	    console.log('counting up...');
	    console.log(n);
	    debugger;
	}

count(3);

Refine the skills covered in this workshop with this training

• Chrome Dev tools documentation
• Google's guide to debugging JavaScript with Chrome Dev Tools