DEV Community

loading...
Cover image for What VS Code extensions am I using?

What VS Code extensions am I using?

André Varandas
I do stuff for the web.
・2 min read

I like to keep VS Code lightweight as much as possible, therefore I don't have that many extensions - only the ones that are really cannot live without.

The more extensions you have, the more memory it will consume, the more time to boot up vs code.

I should also add that my main editor is not visual studio code but Webstorm. I mainly use VS Code for small edits on some JSON or small JavaScript files. Sometimes I may also use VS Code for starting up small side projects, when I want to try something new or some ideas from a blog post I just read.

I love VS Code and I like to keep it ready for hacking. 😊

  1. ESLint - This one integrates ESLint into VS Code.
  2. EditorConfig for VS Code - Adds support for .editorconfig files.
  3. EditorConfigGenerator - I am lazy enough I can't open a new tab and search for a good default .editorconfig so I use this extension to generate the defaults for me.
  4. markdownlint - As I'm usually editting a lot of .md files, this extension informs me about lint errors.
  5. npm - Adds some nice npm scripts options to the command pallete.
  6. npm Intellisense - Adds intellisense on import statements.
  7. Prettier - Code formatter - I really like prettier defaults.
  8. Vetur - Vue tools for VS Code. Most of the time I'm working with Vue, this extension adds a lot of useful snippets as well as syntax highlighting.
  9. GitLens - Git supercharged - Helps to visualize code changes.

And that's it! This is the minimum I need to make VS Code work just as I want for my needs. I used to have a lot more, I even lost track of them, until VS became so slow, I had to revise all of them, removing all the non essential ones.

What are the VS Code extensions you can't live without?

Thanks for reading 👋

Photo by John Barkiple on Unsplash

Discussion (0)