Skip to main content

My Visual Studio Code Setup

by Jessy Cormier - a year ago Tue, 03 Jan 2023 04:00:00 GMT

I’ve found value in finding these kinds of posts by other people online so I thought I would share my setup to maybe benefit you.

User Settings

Here you go! this has everything for code formatting stripped out as that’s a pretty big personal preference here (or project specific). Generally here’s some of the things I tend to use now.

// User/settings.json
    "workbench.colorTheme": "Default Dark+",
    "workbench.iconTheme": "material-icon-theme",
    "editor.rulers": [
    "editor.inlineSuggest.enabled": true,
    "editor.stickyScroll.enabled": true,
    "editor.accessibilitySupport": "off",
    "workbench.editor.labelFormat": "short",
    "workbench.tree.indent": 16,


  • have to have a dark theme I havn’t explored to many that I liked so I usually just stick the to the default.


  • This icon pack was very useful while doing angular development but it’s full of other icons that work for pretty much everything I’ve worked with so it’s been my go to.


  • Following the 80 or 120 line break rule helps out when when working on a team I find. PR’s are easier to review when doing side by side and not overflowing, and generally code is cleaner.


  • Auto suggestions heck yeah save me time whenever I can get it.


  • This newish feature of VScode is awesome. when scrolling down a large file with nested logic you’ll have the “parent” stick on the top of the editor so you know your current context..


  • This one is useful specifically for Sveltekit (or any folder route framework nextjs for example), but I find it helpful for all projects generally. It adds the files folder to the right of the filename in the tab.


  • Simply add in more or less spacing for the file structure tree, I find having a bit more space lets me easily identify files/folders more easily.

That’s about it for specific user settings. Per project I’ll have different rules setup for formatting based on my preferences but heavily consider the projects/frameworks defaults first over my own preferences. I find by trying out different rules I gain a respect for what it solves which is knowledge growth on my part and helps me identify what may be useful for personal vs group work.


  • GitLens
  • Material Icon Theme
  • Peacock this one took some time to fall in love with but it’s become part of my core extensions. It’s useful to use the random color picker for a project so you can identify quickly different projects if you have more than one open.
  • Prettier until I found an option specific for html attribute brackets I had only used it for js/ts but now that I know it can be customized for html the way I like, this is a great thing to have in any project. Set it up so it doesn’t auto do it on document save so you can control when it formats.
  • Random Everything I use this mostly for the UUID generation but it has a ton of other useful things when building out demo content.
  • Svelte for VS Code for building this website of course.
  • Tailwind CSS IntelliSense I built this site using tailwindcss so using this plugin is useful to get context about tailwind like picking colors or what other things are available without having to go look everything up on the docs.
  • Todo Tree This one I’m still in conflict with. The saying goes don’t write todos in code, but in reality sometimes this is the cleariest spot to leave information rather than externalizing it. Especially for future self. This extension makes seeing those todos really easy plus you can customize it to pick up other phrases if you want as well as colour code them when found.
  • Visual Studio Keymap I need this to function effeciently in vscode. I’ve used these keybindings for so long now it would be hard to switch off.

and I have a few disabled based on projects or messing around with to see if I like them. Thunder Client, ESLint to name a few.

Closing Thoughts

Generally I like to try out new things including coding practices to see how it can fit into my workflow or perhaps make teams create more managable code bases. Keeping things close to default I think is important so it applies to a wider group of people but it’s still fantastic to be able to customize as freely as we can in VS code. I think that’s what sets this IDE above a lot of other ones, it’s a fantastic DX (Developer experience).