DEV Community

Cover image for Debugging beyond console.log() in JavaScript
Gautam Vaja for CodeParrot

Posted on • Originally published at 10xdev.codeparrot.ai

Debugging beyond console.log() in JavaScript

Most JavaScript developers are familiar with the basic console.log(). However, the console API offers many other methods that can be incredibly useful in both development and debugging workflows.

Basic console.log()

Let's start with the basic console.log() which is used to print messages to the console.

console.log("Hello, World!");
Enter fullscreen mode Exit fullscreen mode


This is the most commonly used method for debugging and logging messages.

console.error()

console.error() is used to output error messages. It helps in distinguishing errors from regular log messages in the console.

console.error("This is an error message");
Enter fullscreen mode Exit fullscreen mode

This will print the message in red, making it stand out.

console.warn()

console.warn() outputs warning messages. These are less severe than errors but still important to notice.

console.warn("This is a warning message");
Enter fullscreen mode Exit fullscreen mode

Warning messages appear in yellow, which helps to differentiate them from regular logs and errors.

console.info()

console.info() is used for informational messages.

console.info("This is an informational message");
Enter fullscreen mode Exit fullscreen mode

It behaves similarly to console.log() but can be useful for categorizing log messages.

console.debug()

console.debug() is used for debugging purposes and is often hidden by default in many browsers' console settings.

console.debug("This is a debug message");
Enter fullscreen mode Exit fullscreen mode

To enable it make sure that Verbose is checked in the top bar.

console.table()

console.table() allows you to display data as a table. This can be very helpful when working with arrays or objects.

const users = [
  { name: "Alice", age: 25 },
  { name: "Bob", age: 30 },
  { name: "Charlie", age: 35 },
];

console.table(users);
Enter fullscreen mode Exit fullscreen mode

This will print the users array as a table, making it easier to read.

console.time() and console.timeEnd()

These methods are used to measure the time taken for a piece of code to execute.

function processData() {
  console.time("processData");
  // Simulating a time-consuming process
  for (let i = 0; i < 1000000; i++) {
    // Process
  }
  console.timeEnd("processData");
}

processData();
Enter fullscreen mode Exit fullscreen mode

console.time("processData") starts the timer, and console.timeEnd("processData") stops it, printing the time elapsed in milliseconds. This can help identify bottlenecks in code and improve performance.

console.count()

console.count() is used to count the number of times a code block is executed.

for (let i = 0; i < 5; i++) {
  console.count("Counter");
}
Enter fullscreen mode Exit fullscreen mode

This will print the count each time the loop runs.

console.group() and console.groupEnd()

These methods allow you to group together multiple log messages.

console.group("User Details");
console.log("Name: Alice");
console.log("Age: 25");
console.groupEnd();
Enter fullscreen mode Exit fullscreen mode

This creates an expandable group in the console. You can also create nested groups for better organization.

console.assert()

console.assert() writes a message to the console only if an assertion is false.

const x = 10;
console.assert(x > 10, "x is not greater than 10");
Enter fullscreen mode Exit fullscreen mode

Since x is not greater than 10, the message will be printed.

Styling Console Logs

You can style console log messages using CSS.

console.log("%cThis is a styled message", "color: blue; font-size: 20px;");
Enter fullscreen mode Exit fullscreen mode

The %c is a placeholder for the CSS style string that follows.

Best Practices

  1. Use Appropriate Methods: Use console.error() for errors, console.warn() for warnings, and so on. This helps in filtering messages in the console.
  2. Remove Logs in Production: Ensure that you remove or disable console logs in production code to avoid clutter and potential performance issues.
  3. Group Related Logs: Use console.group() and console.groupEnd() to keep related logs together.

Conclusion

Next time you’re knee-deep in code and need to debug, give these methods a try. They can make your life easier and your debugging sessions more efficient. So, go ahead, experiment with these in your next project and see the difference they can make.
For more detailed information, you can refer to the MDN Web Docs on console.

Top comments (17)

Collapse
 
krunalrana profile image
Krunal Rana

console.log(Object.keys(console))

Try this you will get list of functions associate with console function,

Alternat methods :

Using Object.getOwnPropertyNames()
console.log(Object.getOwnPropertyNames(console));

Using for...in loop

for (let key in console) {
console.log(key);
}

*Note : * this is not just console function we can find almost all properties of any JS function

Image description

Collapse
 
mvaja13 profile image
Gautam Vaja

Great

Collapse
 
shricodev profile image
Shrijal Acharya

Never knew about console.time(). Thank you for sharing this. 🙌

Collapse
 
anmolbaranwal profile image
Anmol Baranwal

Yep! Didn't know a lot of stuff. Console hides a lot!
I think using a separator after each point would give a better structure for the post.

Collapse
 
mvaja13 profile image
Gautam Vaja

Thanks for the advice

Collapse
 
yusuke050 profile image
Lin Fan-Chiang

Thank you for sharing. I plan to use console.group() and console.groupEnd() for my next implementation.

Collapse
 
mvaja13 profile image
Gautam Vaja

Yeah go ahead.

Collapse
 
sudipmondal2002 profile image
SUDIP MONDAL

Insightful

Collapse
 
alanoberto profile image
Alan Oberto

Very Nice article, I was not aware of at least half of it

Collapse
 
krunalrana profile image
Krunal Rana

console.time() and console.timeEnd()

is new for me #Helpfull #greateinsight

Collapse
 
emmijozzy profile image
OGUNSUYI JOSEPH OLUWASEUN

Nice

Collapse
 
markwilliams21 profile image
Mark

Thanks for sharing this with us! Keep up the good work.

If you want to know more about java then do visit here

Collapse
 
albertobarrago profile image
alBz • Edited

really nice Article ;-)

Collapse
 
saikumar2121 profile image
Saikumar

it's better to use logging libraries like errsole because you can get insights about your application and see your logs all in one place in the UI

Some comments may only be visible to logged-in visitors. Sign in to view all comments.