Chrome JS Console Basics

My Flatiron cohort has switched from “Ruby mode” to “Javascript mode” for the second half of our program, and among the many changes that come with programming in a different language, one that immediately stood out to me was my set of debugging tools.

Using debugger to pause my functions or console.log to print variable values isn’t so different from Pry and “puts” in Ruby, but the Chrome console–where I have been spending lots of time lately–is quite a change from the Terminal.

There’s a lot to take in when you first open the Chrome Javascript DevTools (press cmd+option+j while in a Chrome window)–html elements, a console, network status codes–all crammed into a side panel. So far, I’ve only made use of a small portion of its functionality, but this weekend I discovered Google’s extensive DevTools guide, and ran through some basic tools that I can make use of right away.

The Google guide is an excellent resource, so I’ll just focus on a few features that help illustrate the power and ease-of-use of some of the basic debugging tools: breakpoints, event listener breakpoints, and step buttons.

A breakpoint can be used to pause the code (just like debugger), but can be set without typing debugger into the js file, refreshing the page, and running the code.


In the above example, my code is paused in a debugger that I wrote into my js file. At this point, I can set a new breakpoint on line twenty by simply clicking on the line number. The line will be flagged in blue when the breakpoint is set. I can then press play to resume script execution until it hits my breakpoint. Play to next breakpoint.png

Once paused at a breakpoint, I can click the console tab and check the value of this.currentRound, for example.

The step buttons allow me move through the code without setting breakpoints. The down arrow steps into the next function call, which means that if the next line of code is a function call, the script will execute and stop at the first line of that next function.

The up arrow steps out of the current function, meaning that it executes the remainder of the function that it’s in, and then stops at the beginning of the next statement after the function call.

The step over (curved arrow) function call executes whatever happens on the next line and moves to that line. Step through.png

Aside from setting breakpoints at specific lines or using step buttons to traverse code, breakpoints can also be set with triggering events, such as a mouse click, or DOM mutation. In my below example, I’m creating a breakpoint to be set upon a timer being fired off.

Set timer.png

The script executes until it hits my function called “countdown” being fired from a setInterval method. From there I can click over to the console tab and do some debugging!

hit event.pngAs I mentioned, these are just a few of the available tools in the Chrome JS console. I highly recommend going through this demo for getting started with debugging JavaScript in Chrome DevTools, which goes through some of the topics I covered here, as well as introducing “watch,” another useful feature for checking changes in a variable.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s