Skip to content
Tutorials Center
My learning

Topics

Lesson 22 of 40 ยท Extensions

Essential Extensions by Task

Choose VS Code extensions by job instead of by popularity: language support, quality tools, Git helpers, themes, and shared recommendations in extensions.json.

"What are the best VS Code extensions?" is the wrong question, because the right list depends on your work. A better question is: which job am I trying to do, and which single extension does it best? This lesson groups extensions by task, explains the difference between a language extension and a helper, and shows how a project can recommend extensions to everyone who opens it.

We cannot run VS Code here, so no real extension is executed. Names below are real Marketplace IDs at the time of writing, but always check the details page, because publishers and names change.

Think in tasks

Pick extensions by task

Language Syntax, IntelliSense, debugging
Quality Format and lint on save
Git History and blame
Look Theme and icons

One good extension per job.

1 / 3

Language extensions

A language extension teaches VS Code about one language: syntax coloring, completions, hover documentation, go to definition, rename and often debugging. Built-in support already covers JavaScript, TypeScript, JSON, HTML, CSS and Markdown, so web developers can start with no extension at all. For other languages you install one:

Language Typical extension What it adds
Python Python (ms-python.python) with Pylance IntelliSense, debugging, test discovery
Java Extension Pack for Java Language server, debugger, Maven/Gradle, tests
C and C++ C/C++ (ms-vscode.cpptools) IntelliSense, debugger
C# C# Dev Kit Language service, solution explorer, tests
Go Go (golang.go) gopls integration, debugging, tests
Rust rust-analyzer Completions, inline type hints, checks
PHP A language server such as Intelephense Completions and diagnostics

Install the official or most widely used one for your language and stop there. Two Python language servers running together only produce duplicate warnings. For how these extensions talk to the editor, see language servers and IntelliSense.

Quality tools

These keep the code consistent:

  • Prettier (esbenp.prettier-vscode) formats JavaScript, TypeScript, CSS, JSON and Markdown.
  • ESLint (dbaeumer.vscode-eslint) shows lint problems as squiggles.
  • EditorConfig for VS Code reads .editorconfig so every editor agrees on tabs and line endings.
  • Code Spell Checker flags typos in identifiers and comments.

The next lesson, formatters and linters, shows how to set them up so they do not fight each other.

Helpers worth knowing

  • GitLens adds blame annotations and rich history on top of the built-in Git features (see source control basics).
  • Live Server serves static HTML with reload on save.
  • Markdown All in One adds shortcuts and a table of contents for Markdown.
  • Error Lens prints diagnostics at the end of the line.
  • Docker and Kubernetes extensions add file support, explorers and commands.
  • Remote extensions for SSH, WSL and containers (Remote SSH and WSL, dev containers).

You do not need all of them. A good starter set is the language extension, a formatter, a linter and one helper you actually miss.

Sharing recommendations with extensions.json

A project can list the extensions it expects. Create .vscode/extensions.json:

JSON
{
  "recommendations": [
    "esbenp.prettier-vscode",
    "dbaeumer.vscode-eslint",
    "editorconfig.editorconfig"
  ],
  "unwantedRecommendations": [
    "hookyqr.beautify"
  ]
}

When someone opens the folder, VS Code offers to install the recommendations. Commit the file to Git. unwantedRecommendations hides an extension that conflicts with the team's formatter. In the Extensions view, @recommended shows the list.

This does not install anything silently; each person chooses. That is intentional, because installing code from a repository without consent would be unsafe.

Extension packs

An extension pack is an extension that only bundles other extensions. "Extension Pack for Java" is the best-known example: install one item, get six. Uninstalling the pack leaves the members installed, so remove them separately if you want them gone.

A runnable stand-in: compare team and personal lists

This script does what a good onboarding script could do with code --list-extensions output and the project's recommendation list. It is plain JavaScript and does not call VS Code.

JS Stand-in: which recommended extensions are missing?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

JS Stand-in: detect overlapping extensions

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where does a project list the extensions it recommends?

    .vscode/extensions.json holds the recommendations array. launch.json is for debugging.
  2. 2. Does VS Code install recommended extensions automatically?

    VS Code only offers the recommendations. Nothing is installed without the user's consent.
  3. 3. What does an extension pack do?

    A pack only lists other extensions; installing it installs the members.
  4. 4. Which is the best approach to language support?

    Duplicate language servers produce duplicate or conflicting diagnostics.

Summary

  • Choose extensions by task: language, quality, Git, look and feel.
  • Built-in support covers web basics; most other languages need one extension.
  • .vscode/extensions.json shares recommendations and can hide unwanted ones.
  • Packs bundle extensions; remove members separately.
  • Avoid overlapping extensions, and review the list now and then.

Next: Formatters and Linters