Productive VS Code - Lesson #55

console.log() Faster with Turbo Console Log

I've recently been live-coding on Twitch and the thing that I've loved about it is all the users in the chat that are helping me out by giving me their own tips and tricks.

In our most recent stream, we started talking about my VS Code extensions and one that was recommended to me that I'd never heard of before was Turbo Console Log.

Turbo Console Log in the VS Code Marketplace

In a nutshell, it lets you take a variable and quickly write the whole console.log statement with keyboard shortcut ctrl + alt + l for Windows or cmd + opt + l for Mac.

Here's a gif of it in action:

Turbo Console Log in Action

I'm a sucker for any keyboard shortcut that can save me from writing some characters. Absolutely love working with Vim.

  • If you told me of an extension or keyboard shortcut that saved me typing even 3 characters, I'll jump on it and dedicate adding that to my arsenal of keyboard shortcuts.

The JavaScript (ES6 Code Snippets) extension has a convenient snippet where you can type:

javascript
// snippet activation 
clg

// expands to
console.log()

Turbo Console Log provides another convenient shortcut to create those console.logs.

In addition to creating console.log() messages quickly, Turbo Console Log can:

  • Delete all console.log() messages: shift + alt + d
  • Comment all console.log() messages: shift + alt + c
  • Uncomment console.log() messages: shift + alt + u
Turbo Console Log in the Command Palette

Yes I know that the Debugger for Chrome extension is useful also to find out what is in your code, but sometimes you just gotta console it!

Want to improve your coding and design skills?

I'm continually researching the best practices and tools for coding.
Join 50,000+ developers looking to make cool stuff.

We value your privacy. 1-click unsubscribe.

Chris Sev

Chris Sev

Chris Sev is the co-founder of Better Dev. Coding better every day. Previously he created Scotch.io which was acquired.

Comments

What did you think of the article? Let us know!
(these comments are powered by GitHub issues and use 0 trackers)