March 2022 (version 1.66)
🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. March 2022 (version 1.66) Update 1.66.1 : The update addresses these issues . Update 1.66.2 : The update addresses these security issues . Downloads for 1.66.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the March 2022 release of Visual Studio Code.
There are many updates in this version that we hope you'll like, some of the key highlights include: Local history - Keep track of local file changes independent of source control. Settings editor language filter - Displays available language-specific settings. Terminal find improvements - Matches are highlighted in the terminal panel and scroll bar. Built-in CSS/LESS/SCSS formatters - Code formatting for CSS, LESS, and SCSS.
JavaScript heap profiles - Collect and view JS memory allocations while debugging. VS Code for the Web - Drag and drop files and folders into vscode.dev. Remote - SSH support for Mac - Connect via SSH to Apple Silicon/M1/ARM64 machines. New R language topic - Learn how to use R for data science in VS Code. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Watch the release party: Listen in as the VS Code team discusses some of the new features.
You can find the recording of the event on our YouTube channel. Highlights short: If you just have 60 seconds, check out the March VS Code release highlights video to quickly see what's new. Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. Accessibility The team works hard to make VS Code one of the most accessible editors available.
This release contains several improvements to help usability and accessibility: Reduce motion mode - Limit animations used in the VS Code UI. More visible source control decorators - Higher visibility using patterns and color contrast. Audio cues volume control - You can now adjust the editor audio cue volume. Comment UI accessibility - New commands and keyboard shortcuts. High Contrast Light color theme - Theme authors can now contribute colors to High Contrast Light.
Workbench Local history Local history of files is now available in the Timeline view. Depending on the configured settings, every time you save an editor, a new entry is added to the list: Each local history entry contains the full contents of the file at the time the entry was created and in certain cases, can provide more semantic information (for example, indicate a refactoring). From an entry you can: Compare the changes to the local file or previous entry.
Restore the contents. Delete or rename the entry. There are new global commands to work with local history: workbench.action.localHistory.create - Create a new history entry for the active file with a custom name. workbench.action.localHistory.deleteAll - Delete all history entries across all files. workbench.action.localHistory.restoreViaPicker - Find a history entry to restore across all files. These commands don't have default keybindings but you can add your own keyboard shortcuts .
There are also new settings to work with local history: workbench.localHistory.enabled - Enable or disable local history (default: true ). workbench.localHistory.maxFileSize - File size limit when creating a local history entry (default: 256 KB ). workbench.localHistory.maxFileEntries - Local history entries limit per file (default: 50 ). workbench.localHistory.exclude - Glob patterns for excluding certain files from local history. workbench.localHistory.mergeWindow - Interval in seconds during which further changes are added to the last entry in local file history (default 10s ).
A new filter action in the Timeline view toolbar allows you to enable or disable individual providers: Note: Local history entries are stored in different locations depending on your use of VS Code. When opening local files, the entries are persisted in the local user data folder and when opening remote files, they will be stored on the remote user data folder. When no file system is available (for example, in certain cases when using VS Code for Web), entries are stored into IndexedDB.
Settings editor Language filter Users can now type @lang:languageId in the Settings editor search box to view and edit all settings that can be configured for the language with ID languageId . This way, users can view language-specific settings, also known as language overrides. Note that these overrides remain configured until explicitly reset by clicking in the gear icon and resetting the setting. The short video below has the language filter set to @lang:css to display all possible CSS language override settings.
Theme: Light Pink Workspace and Folder settings preservation Workspace and folder settings in the Settings editor are now preserved until manually reset by the user. This change helps the case where the user wants to explicitly specify a workspace setting value that is equal to the default value of a setting, but is different from the user setting value. Previously, users had to open the workspace settings JSON file to set this value.
Below the editor tab size is set in Settings editor Workspace tab and it is automatically added to the workspace's settings.json file. Theme: Light Pink Primary notification buttons The first button of a notification now appears with a primary color to distinguish from other buttons. This follows the same patterns as dialogs. Theme: GitHub Dark New context keys for editors There are new context keys indicating whether an editor is the first or last in an editor group: activeEditorIsFirstInGroup - Whether the active editor is the first one in its group. activeEditorIsLastInGroup - Whether the active editor is the last one in its group.
These context keys can be used to conditionally enable keyboard shortcuts using when clauses . Default binary editor A new setting, workbench.editor.defaultBinaryEditor , lets you circumvent the binary file warning and automatically open the editor type of your choosing when a binary file is detected. You can select the default binary editor ID from a dropdown in the Settings editor or via IntelliSense in settings.json .
Smoother authentication experiences You may notice smoother authentication flows of both GitHub and Microsoft. For GitHub authentication, we've removed the initial Continue page so your log in experience requires one less step. For Microsoft authentication, we try to minimize the number of times you are sent out of VS Code to log in, if you've already logged in with Microsoft for Settings Sync or another extension. Install pre-release and normal extensions together from CLI VS Code now supports installing pre-release and normal extensions together from the command line.
For example, the following command line instruction will install the pre-release version of GitHub.vscode-pull-request-github extension and release version of GitHub.remotehub extension: code --install-extension GitHub.vscode-pull-request-github@prerelease --install-extension GitHub.remotehub Improved platform specific extension updates VS Code now supports updating a platform specific extension to a more specific target platform version.
For example, if you are on Windows 64-bit and have installed the C/C++ extension for Windows 32-bit and the Marketplace has the extension with same version for Windows 64-bit, VS Code will automatically update the extension to the 64-bit version. Audio cue improvements The new setting audioCues.volume (0-100, default is 50) can be used to control the volume of audio cues. There is also an updated audio cue for folded regions.
New names for Side Panel and Side Bar Two releases ago, we introduced the Side Panel . At that time, we removed the capability to move the bottom panel that contains the terminal to the side
The rest of this page is on the live site.