My VS Code Setup for TypeScript Development in 2026
January 10, 2026
•
5 min read
People always ask what tools I use. Here's my complete VS Code setup for TypeScript development, the extensions, settings, and workflows that help me ship code faster without burning out.
This isn't about having the most tools. It's about having the right tools, configured to stay out of your way until you need them.
The Philosophy
Three principles guide my setup:
- Automate the obvious: Formatting, imports, and linting should happen without thinking
- Surface the important: Errors, types, and git status should be visible at a glance
- Stay fast: Every millisecond of lag compounds into frustration
With that in mind, let's dive in.
Essential Extensions
Code Quality
ESLint: The foundation of code quality. Combined with TypeScript's compiler, this catches 90% of issues before they become bugs.
Prettier: Formatting wars are over. Let the robot decide, and never think about tabs vs spaces again.
Error Lens: Displays errors and warnings inline, right next to the problematic code. No more squinting at the bottom panel.
TypeScript Superpowers
Pretty TypeScript Errors: Transforms TypeScript's notoriously cryptic error messages into readable, formatted output. Game changer for complex generic types.
TypeScript Importer : Automatically adds imports when you use a symbol that isn't imported. Saves countless keystrokes.
Move TS: When you rename or move a file, this updates all imports across your project. Essential for refactoring.
Framework-Specific
Angular Language Service: If you're writing Angular, this is non-negotiable. Gives you autocomplete, error checking, and navigation in templates.
ES7+ React/Redux/React-Native snippets: Quick scaffolding for React components and hooks.
Tailwind CSS IntelliSense: Autocomplete for Tailwind classes, with color previews and documentation on hover.
Git & Collaboration
GitLens: See who wrote each line, when, and why. Invaluable for understanding legacy code or tracking down when a bug was introduced.
GitHub Copilot: AI pair programming. Controversial, maybe, but it's genuinely useful for boilerplate, tests, and documentation.
Quality of Life
Auto Rename Tag: Rename an HTML/JSX opening tag, and the closing tag updates automatically.
Bracket Pair Colorizer (now built-in): Different colors for nested brackets. Makes complex expressions parseable at a glance.
Path Intellisense: Autocomplete for file paths in imports. Never type ../../../ and get it wrong again.
Code Spell Checker: Catches typos in variable names, comments, and strings. Embarrassment prevention.
Settings I Can't Live Without
Here's my complete settings.json, with explanations:
Custom Keybindings
Speed comes from muscle memory. These are the keybindings I've internalized:
Color Theme & Icons
I switch between two themes depending on lighting:
- Day: GitHub Light (easy on the eyes in bright rooms)
- Night: One Dark Pro (classic, high contrast)
For file icons: Material Icon Theme. Makes scanning the file tree much faster.
Snippets That Save Time
Custom snippets for patterns I type constantly:
The Workflow
Here's how these tools come together in practice:
- Start a feature: Cmd+Shift+P → Git: Create Branch
- Find a file: Cmd+P → type part of the name
- Navigate code: Cmd+Click on any symbol
- Refactor: F2 to rename, then check all references with Shift+F12
- Commit: Open terminal (Cmd+``), run git add . && git commit`
- Review changes: GitLens shows the diff inline
The key is staying in the editor. Every context switch—to browser, to terminal, to another app—costs mental energy. The more you can do without leaving VS Code, the faster you move.
What I Don't Use
Equally important is what I've removed:
- Too many extensions: Each one adds startup time and potential conflicts
- Heavy themes: Fancy animations slow things down
- Overloaded status bar: I hide most status bar items
- Extension packs: Install only what you actually use
Less is more. A lean setup is a fast setup.
Try It
Here's a quick way to bootstrap this setup:
Then copy the settings above into your settings.json. Give it a week, and you'll wonder how you coded any other way.
What's in your setup? I'm always looking for new tools and workflows. Drop me a message (opens in new tab) with your favorites.