Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

How to go beyond console.log and get the most out of your browser’s debugging console

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

The console object is a very useful feature of browsers that have been around for many years. It provides access to the browser’s debugging console.
Most web developers know how to print messages to the console using console.log.  But I’ve found that many don’t know about other features of the console, even though they can be very useful for every web developer.

In this post, I’ll go over some of these lesser-known features and capabilities. I hope that you will find them useful and interesting, and will incorporate them into your day-to-day workflow and code.

I added a screenshot of the result of each example. If you want to try things for yourself, just open the DevTools and copy-paste the examples.

Using multiple arguments

It is quite common to log several values together. These may be a message along with a related value or the content of several related variables.

Here are two ways I’ve seen developers achieve this:

1. String concatenation

const a  123;
const b  'abc';
const c  {aa: 234, bb: 345};
console.log('Foo bar ' + a + ' ' + b + ' ' + c);
 
Result of string concatenation
Result of string concatenation

2. Using multiple calls

const a  123;
const b  'abc';
const c  {aa: 234, bb: 345};
console.log('Foo bar');
console.log(a);
console.log(b);
console.log(c);
 
Result of multiple calls Result of multiple calls

These methods may work (sort of), but:

  • They are not flexible
  • They are not very readable
  • They are cumbersome to write
  • They need special means to work properly with object variables

There are several better alternatives for outputting many variables. The most useful one for quick data dump is sending multiple arguments to console.log like so:

const a  123;
const b  'abc';
const c  {aa: 234, bb: 345};
console.log('Foo bar', a, b, c);
 
Result of multiple arguments Result of multiple arguments

This is very handy for debugging, but the output is not very controllable. For output that is intended to be read (like for a library), I would use a different method, which we’ll get to later on.

Using different log levels

Besides the familiar console.log, there are other logging methods that correspond to different log levels:

console.debug('Debug message');
console.info('Info message');
console.log('Good old log message');
console.warn('A warning message');
console.error('This is an error');
 
Log levels as seen in Google Chrome Log levels as seen in Google Chrome

Each log level may have a different default style, which makes spotting errors and warnings at a glance easier.

You can usually also filter which log levels you want to be visible in the DevTools console. This may help reduce clutter.

 
Filtering log levels in Google Chrome Filtering log levels in Google Chrome

The appearance of the different levels and the filtering granularity changes from browser to browser.

Grouping console lines

Sometimes it is useful to group log messages together. It may allow for more organized and readable output.

This is actually very simple to achieve:

console.group();
console.log('First message');
console.log('Second message');
console.groupEnd();
 
Grouped log messages Grouped log messages


Note that log groups can also be nested and labeled:

console.group('Group aaa');
console.log('First message');
console.group('Group bbb');
console.log('level 2 message a');
console.log('Level 2 message b');
console.groupEnd();
console.log('Second message');
console.groupEnd();
 
Nested and labeled groups Nested and labeled groups

In case you want the group to appear collapsed, use console.groupCollapsed()

Measuring performance

Measuring the time between points in the code can serve as a quick way to check the performance of some operations.

Here is a trivial way to do this:

const start  Date.now();
// do some stuff
console.log('Took ' + (Date.now() - start) + ' millis');

This works, but there’s a more elegant way to achieve something similar:

console.time('Label 1');
// do some stuff
console.timeEnd('Label 1');
 
Measuring time with the console Measuring time with the console

The code is shorter, the measurement is more accurate, and you can keep track of up to 10,000 different timers in parallel on a page.

String substitution

Previously we learned that you can pass multiple arguments to console.log to output multiple values simultaneously. Another way to achieve something similar is to use string substitution. This method requires familiarity with the available placeholders but offers greater control over the output.

const a  123;
const b  'abc';
const c  {aa: 234, bb: 345};
console.log('number %d string %s object %o', a, b, c);
 
Logging with string substitution
Logging with string substitution

Take a look at the documentation (link at the end) for a list of available placeholders.

Styling

It can be nice to style different log messages differently to increase readability.

We already mentioned that browsers give different default styling to some log levels, but this can also be customized according to your specific needs. Styling is done using a subset of CSS rules, passed in a string as the second parameter, and applied using the marker %c.

Note that you can have different styles for different parts of the log message.

For example:

console.log("Normal %cStyled %clorem %cipsum", "color: blue; font-weight: bold", "color: red", "background-image: linear-gradient(red, blue); color: white; padding: 5px;");
 
Styled log messages Styled log messages

Summary

In this post, we have seen some of the features of the console that I think are less well-known and more useful. This is by no means an exhaustive list of everything the console can do, as it has many more tricks up its sleeve.

If this got you interested and you want to find out what other things you can do with the console, I recommend reading the relevant documentation on MDN and trying things out in DevTools.

Subscribe for Email Updates:

Categories:

Tags:

Agile Basics
Reading List
LAB
Jira admin
Jira Cloud
IT Operations
Lean Agile Management
Agile Delivery
Atlassian
Enterprise DevOps
Professional Scrum with Kanban
Scaled Agile Framework
Continuous Improvement
SAFe DevOps
Atlaassian
LPM
ATDD
GanttBan
Sprint Iteration
Coaching Agile Teams
Change Management
Kanban Game
Scrum Master
Operational Value Stream
Lean and Agile Techniques
Nexus vs SAFe
Agile Exercises
Agile Release Planning
Program Increment
Effective Agile Retrospectives
Lean Agile
lean agile change management
Engineering Practices
SA
Portfolio for Jira
Built-In Quality
ScrumMaster Tales
Risk Management in Kanban
Presentation
Agile Project
PI Planning
Tips
Product Management
Jira
Release Train Engineer
Legacy Code
TDD
Lean Risk Management
POPM
Confluence
Nexus
Iterative Incremental Development
Lean Agile Organization
A Kanban System for Software Engineering
Managing Risk on Agile Projects
Video
Continuous Integration
The Agile Coach
Kanban 101
Spotify
Scrum.org
System Archetypes
WIP
Agile Games and Exercises
Lean Agile Basics
Agile Israel Events
RTE
Scrum Values
SPC
Agile Techniques
Daily Scrum
speed at scale
Value Streams
Risk Management on Agile Projects
AI
Amdocs
RTE Role
Continuous Delivery
Manage Budget Creation
Principles of Lean-Agile Leadership
Scrum
Covid19
Lean Agile Leadership
Software Development
transformation
Applying Agile Methodology
Lean Software Development
Rovo
Agile Program
Quality Assurance
Agile Assembly Architecture
Accelerate Value Delivery At Scale
Agile Risk Management
AgileSparks
Agile Outsourcing
Slides
Kanban
Scrum and XP
Entrepreneurial Operating System®
Process Improvement
Lean-Agile Budgeting
Lean and Agile Principles and Practices
Retrospectives
Introduction to Test Driven Development
Continuous Deployment
NIT
agileisrael
Agile Marketing
ROI
The Kanban Method
Scrum Guide
Large Scale Scrum
Frameworks
User stories
Lean Budgeting
Agile India
Advanced Roadmaps
LeSS
Product Ownership
Story Slicing
Test Driven Development
Pomodoro Technique
PI Objectives
predictability
SAFe
QA
Risk-aware Product Development
Implementation of Lean and Agile
Agile Testing Practices
Agile for Embedded Systems
Agile Product Ownership
Webinar
Software Development Estimation
Development Value Streams
Team Flow
Business Agility
Elastic Leadership
Agile Product Development
Nexus Integration Team
Nexus and SAFe
Tools
What Is Kanban
ART Success
Professional Scrum Product Owner
Agile and DevOps Journey
Self-organization
Kanban Kickstart Example
Games and Exercises
Acceptance Test-Driven Development
ATDD vs. BDD
Agile Games
speed @ scale
Kanban Basics
Keith Sawyer
System Team
Agile Release Management
Managing Projects
ARTs
Kaizen Workshop
AI Artificial Intelligence
Agile Project Management
Achieve Business Agility
Agile Community
Legacy Enterprise
Scrum With Kanban
BDD
Certification
Lean-Agile Software Development
Sprint Planning
Lean Startup
Kaizen
Agile Contracts Best Practices
RSA
An Appreciative Retrospective
Implementing SAFe
Scrum Master Role
System Integration Environments
EOS®
Agility
Scrum Primer
chatgpt
Agile Development
Releases Using Lean
Perfection Game
Artificial Intelligence
ALM Tools
Agile
Introduction to ATDD
Agile Mindset
SAFe Release Planning
Code
Limiting Work in Progress
Sprint Retrospectives
Rapid RTC
Jira Plans
Hybrid Work
Nexus and Kanban
Continuous Planning
Agile Israel
Certified SAFe
Planning
Agile in the Enterprise
DevOps
Systems Thinking
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart