Visual Studio Code v1.34 Changelog

This update is mostly about making life easier for developers working in complex setups. If you write code that runs on a different computer than your laptop, or if you build tools for VS Code itself, this release gives you some powerful new ways to work without leaving your local editor.

What's new

• Remote Development (Preview): This is a big deal. It lets you use VS Code on your laptop to write code that lives somewhere else—like a remote server over SSH, a Linux environment on Windows (WSL), or inside a Docker container (a lightweight, isolated package for running apps). It feels like the code is right on your computer, even though it isn't.
• Stop all tasks at once: If you have multiple background jobs running (like watchers that auto-update your code), you can now kill them all with a single command instead of stopping them one by one.
• Debug sub-sessions in the toolbar: When you're debugging (finding and fixing bugs), you sometimes start a "sub-session" (a debugging session inside another debugging session). There's a new setting to show these in the toolbar. If you leave it off, stopping the sub-session will also stop the main one, which keeps things simple.

Improvements

• CodeLens caching: CodeLens shows extra info above your code (like how many times a function is used). Before, when you switched between files, these lines would jump around for a second. Now VS Code saves their spots so they appear instantly and stay put.
• Smarter CSS autocomplete: When typing CSS, those weird browser-specific tags that start with a dash (like -moz- or -ms-) will now show up lower in the suggestion list. The standard tags (like grid) get priority, so you don't accidentally pick a weird one.
• Better Vue.js support: The Vetur extension (a popular tool for Vue.js web developers) got smarter. It can now understand JavaScript inside Vue's HTML-like templates, helping you jump to definitions and find references. It also uses less memory and can finish your import file paths for you.
• Multi-extension debugging: If you build add-ons for VS Code, you can now test multiple connected extensions at the same time. Before, you could only test one at a time, which was annoying if your extensions relied on each other.
• Machine-specific settings for add-ons: Extension creators can now mark certain settings (like file paths) as "machine-specific." This prevents settings from getting messed up if you share your setup across different computers.

Fixes

No specific bug fixes were highlighted in these release notes beyond the CodeLens jumping issue mentioned above.

Breaking changes

No breaking changes in this release.