DEV Community

Cover image for Make VS Code better by editing and updating some settings
Jacob Cofman
Jacob Cofman

Posted on • Edited on • Originally published at jcofman.de

Make VS Code better by editing and updating some settings

This article describes five tips on how to make
VS Code development experience a bit better (at least for my kind
of use cases -> Frontend Development) by enabling and editing some settings which are not set by default. You can go to your
settings and enable each one of these by either opening it up via the command palette

  1. CMD + ⌘ + P
  2. Type in settings
  3. - 3. Select Open Workspace Settings (JSON)

or with the shortcut (CMD + ,) and click on the icon Open Settings (JSON) on the upper right corner.

Here are the five πŸ”₯ things I add to improve my development environment.

1. Enable bracket colorization

Using bracket colorization makes it easier to see where code blocks start and end.

// settings.json

// 1. enables vscode native bracket colorization
 "editor.bracketPairColorization.enabled": true
Enter fullscreen mode Exit fullscreen mode

2. Enable bracket pair guides

Besides using bracket colorization, I love to add bracket pair guides.

// settings.json

// 2. enables vscode pair guides
"editor.guides.bracketPairs": true,
Enter fullscreen mode Exit fullscreen mode

3. Highlight modified Tab

I like to make it more clear which file I work on.

// settings.json

// 3. highlight active tab
"workbench.editor.highlightModifiedTabs": true,
Enter fullscreen mode Exit fullscreen mode

4. Using Font Ligatures

It makes it easier to distinguish comparisons between code lines.

// settings.json

// use a font with font ligatures
"editor.fontFamily": "Jetbrains Mono, Menlo, Monaco, 'Courier New', monospace",
// 4. enable font ligature
"editor.fontLigatures": true,
Enter fullscreen mode Exit fullscreen mode

5. Enabling Inlay hints

It can help you see what properties need to get passed into functions. without having to hover over the function call.

// settings.json

// 5. enable parameter hints
"typescript.inlayHints.parameterNames.enabled": "all",
Enter fullscreen mode Exit fullscreen mode

Latest comments (24)

Collapse
 
coinzdude profile image
coinzdude

Amazing. Would love to see a compilation of this, and others suggestions in the thread here

Collapse
 
mmoutih profile image
marouane moutih

it's the little things that make a big difference, thnaks a lott

Collapse
 
iniisking profile image
iniisking

Not everyone uses a Mac. There's no guide for Windows users.

Collapse
 
marcogiuliani89 profile image
Marco Giuliani

It's the same,
with Ctrl+Shift+P
rather than CMD + ⌘ + P

Collapse
 
boshrajaber profile image
Boshra Jaber • Edited

Great ones, I would like to add some of my favorite settings as well:

 // settings for auto format on paste, save, and type
 "editor.formatOnPaste": true,
    "editor.formatOnSave": true,
    "editor.formatOnType": true
Enter fullscreen mode Exit fullscreen mode
Collapse
 
erlanggadewa profile image
Erlangga Dewa Sakti

number 5 is so awesome, thanks sir

Collapse
 
randellbrianknight profile image
Randell Brian Knight

Awesome, Thanks

Collapse
 
robbecl profile image
RobbeCl

I love this setting "typescript.inlayHints.parameterNames.enabled", thanks! :-)

Collapse
 
timmortal profile image
Timmortal

(at least for my kind
of use cases -> Frontende Development)

I see a typo, an extra "e" after Frontend

Collapse
 
alsidneio profile image
alsidneio

This is dope. It's always the little things that make a big difference.

Collapse
 
jacksonkasi profile image
Jackson Kasi

very thanks @jcofman i like this theme πŸ₯°βœŒ