Originally posted on dev
Visual Studio Code is a powerful editor out of the box, but there are many many VS Code extensions to make it even more powerful!
If you’re new to VS Code or coding in general, I recommend reading through everything here to see if there are new ways you can optimize your workflow. If you’re a VS Code veteran, see if there’s anything here you don’t have, and let me know in the comments if I missed anything!
VS Code is constantly updating, and I regularly review my extensions to figure out which ones are and are not adding value. I’ll be keeping this list updated as I add and remove extensions.
Better Comments shows your comments as different colors depending on how they’re prefixed. Great to quickly visually scan and identify important pieces of your code. Keep in mind these colors only show if you have the extension, so this is best for personal use cases.
Have you ever been working on a feature that involves 10 functions across several files, forcing you to hop around and re-find each function? Bookmarks helps you keep track of all the code that’s important to you. Just add a bookmark to easily find your spot later!
Trying to find missing parenthesis is my least favorite programming activity. Luckily, Bracket Pair Colorizer makes this a lot easier by color-coding all corresponding parenthesis and brackets. (NOTE: This one has some known performance issues, and theres a beta version of Bracket Pair Colorizer 2 out to fix this. Thanks for the tip, @garret_alex)
change-case gives an easy way to change a word or variable name to all sorts of cases including
TitleCase, and more!
Code Spell Checker finds typos and misspelled words, even if they’re in the middle of a variable name. This is one I didn’t truly realize the value of until I had it installed and started finding all my little typos. Turns out, having a spell checker in a code editor is just as useful as having one in a word processor!
ES7 Snippets has so many useful tools for autofilling in boilerplate text. Saves a ton of time whenever I’m writing imports or React components.
GitLens is a feature-packed extension that gives you all sorts of insight into your repository’s commit history. Personally, I use it most often to see who wrote code inline, see previous versions of files, and compare HEAD to other commits/branches.
If you’re a React developer, you probably often find yourself breaking out large components into smaller ones in separate files as well as switching between class and functional components. glean automates all this for you and automatically inserts all the needed boilerplate.
Import Cost helps you to be cognizant of the size of your imports. It shows the size of each import inline, and shows in red and yellow warning colors if the import is larger than normal.
indent-rainbow makes it effortless to see indents at a glance. Plus, it’s super pretty, right?
console.log()statements into your code, complete with the plaintext variable name and variable value. There’s even a hotkey to remove all
console.log()statements when you’re done with them!
This one’s important. I’d even go as far as to say that nobody should code without Prettier. Prettier auto-formats your code with
F, or you can have it auto-format on every save. This saves a TON of time over remembering every semicolon and indent.
Ever work in a large codebase trying to figure out how to reference another file? Exactly how many
../‘s do you need to get back to the proper directory, then what’s the path back down? Relative Path lets you search all files and auto-inserts the path relative to the file you’re in. No tree counting needed!
There’s not a great way to demo this one, so here’s my favorite gif of all time instead:So, about the extension: When you’ve got a sweet setup in your editor, Settings Sync gives a painless way to sync all your VS Code settings and extensions across your workstations by saving your configuration to a GitHub gist. They’ve even made several improvements over the past year to make syncing/authentication much easier.
With Toggle Quotes, just use
') to cycle your strings between using
It can be a hassle to keep track of all the latest versions of your npm packages. Version Lens shows you inline how your installed versions in
package.jsoncompare to the current versions.
These items don’t dramatically improve my day-to-day productivity, but golly, I sure do like them:
- Dracula Offical – my preferred color theme
- file-icons – gives unique file icons to quickly identify types in the file browser. I find it most useful for quickly distinguishing between
- Fira Code – a spiffy-looking font that includes some sweet ligatures! This means that inequality symbols such as
!==show up as a single character. It hasn’t improved my coding, per se, but it has made me feel cooler.NOTE: Ligatures can be a controversial topic among coders. My argument for using them is that I think they’re sexy. I rest my case.
- Vim – When I first started coding, I got really into becoming a Vim editor power user. The functionality of VS Code goes far beyond the utility I get from Vim, but sometimes I miss those old “Change 100 lines with 5 cryptic keystrokes” features. I mostly leave this disabled, but I fire it up every once in a while when I’m feeling spunky.
Sometimes I stop using an extension because the functionality is added to base VS Code, or maybe the extension isn’t as useful as I once thought it was. Here are some extensions I used heavily once, but eventually uninstalled:
- Indenticator – provided a great way to visually see your indents using highlighted vertical lines. This now comes standard in VS Code, though there are some differences. VS Code Native settings:
- Auto-close tag & Auto Rename Tag – automatically provided closing HTML tags whenever you typed an opening tag, and kept them updated to match each other. Most of this functionality is now included in VS Code, and these plugins were known to cause big performance issues (thanks for the tip, Matt Waler). Native VS Code settings:
- Color Highlight – Highlights any CSS color values with the color they represent. VS Code now natively shows a colored box next to the value, which is good enough for me: