VS Code Setup and WSL2 IntegrationLesson 5.3

Which VS Code extensions every developer should install

Prettier formatter, ESLint, GitLens, Path Intellisense, Error Lens, Remote WSL, Thunder Client, extension sync, disabling extensions per workspace

Essential VS Code Extensions

Extensions are installed per environment in WSL2 — some go on the Windows side (themes, keymaps) and some on the WSL2 remote (linters, formatters, language support). VS Code will prompt you when a local extension should be installed remotely.

Install from the terminal

code --install-extension esbenp.prettier-vscode
code --install-extension dbaeumer.vscode-eslint
code --install-extension eamodio.gitlens
code --install-extension christian-kohler.path-intellisense
code --install-extension usernamehw.errorlens
code --install-extension rangav.vscode-thunder-client

What each one does

Prettier formats code on save. ESLint shows linting errors inline. GitLens adds git blame, history, and diff views directly in the editor. Path Intellisense autocompletes file paths. Error Lens shows error messages inline next to the code. Thunder Client is a lightweight REST API client inside VS Code.

Sync extensions across machines

Open Command Palette, Settings Sync: Turn On, and sign in with your GitHub or Microsoft account. Settings, keybindings, and extensions sync automatically across all your VS Code instances.