Highlights from VSCode 1.61
The open source VSCode project, along with VSCodium, completed their latest monthly release with v1.61. For those of us that haven’t been using the Insider’s Build, it’s time to look at what’s new.
Locked editor groups
Note: this is an experimental feature.
Don’t lose track of a file or terminal you are bouncing back-and-forth between in your gigantic list of editor tabs: use locked editor groups. These prevent VSCode from opening more editor tabs in a group (a collection of tabs).
I like this feature, as I’m often opening new files in the wrong area of the screen. I want those side-by-side, computer!
- Release Party: Editor and workspace improvements demo
Split an editor without creating a new group
Do you find yourself looking at large files, and wish you could scroll down while staying in place elsewhere? Now you can, by doing the splits without creating a new group. Test it out with View: Split Editor in Group
in the command palette (Ctrl+Shift+P
) or with the keybinding shortcut: Ctrl+K Ctrl+Shift+\
. This is useful when converting pieces of code into functions, trimming fat, copy/pasting comment blocks, and whatever else your heart desires.
No new group means not having yet another tab open in your editor!
- Release Party: Editor and workspace improvements demo
Webview UI Toolkit for Visual Studio Code
For extension authors making use of the webview API for customizable views in the editor, life is about to become easier: say hello to the Webview UI Toolkit. This is an open-source component library, providing Visual Studio Code design language, which matches the look and feel of VSCode/VSCodium. This is compatible with your tech stack of choice, bet it React, Vue, or OMGNewJSFramework!
Other notables
General tip: Wondering what shortcuts are configured in VSCode? One shortcut to rule them all:
Ctrl+K Ctrl+S
, orCtrl+Shift+P
-> Preferences: Open Keyboard Shortcuts
- Confusion was caused by a new telemetry config option,
telemetry.telemetryLevel
, which would display that telemetry was enabled (even if it was previously disabled). The full discussion can be found on GitHub, which led to improvements being implemented in the1.61.1
update. - Platform-specific extensions: no longer try installing a MacOS-only extension on your Windows system, or vice-versa. That is, if the extension developer specifies the supported OS targets. This was previewed at the release party.
- I often came back to my laptop to find that my terminal was having a stroke in the VSCode editor. This seems to be resolved!
- The latest point releases (1.61.1 and 1.61.2) include fixes for other problems, such as high CPU consumption. Make sure to keep up-to-date!
I can’t forget: want to take a look at VSCode in your web browser, without installing a thing? These are called Virtual Workspaces, such as vscode.dev and github.dev. Reference the VSCode Blog Post on vscode.dev for a full rundown on bringing VSCode to the browser.