October 2021 (version 1.62)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. October 2021 (version 1.62) Update 1.62.1 : The update addresses this security issue . Update 1.62.2 : The update addresses these issues . Update 1.62.3 : The update addresses these issues . Downloads for 1.62.3 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the October 2021 release of Visual Studio Code.
In addition to releasing a preview of vscode.dev , we announced in the October iteration plan that we would focus on housekeeping GitHub issues and pull requests (see our issue cleanup guide ). Across all of our VS Code repositories, we closed (either triaged or fixed) 4163 issues. While we closed issues, you created 2222 new issues. The main vscode repository now has 2491 open feature requests and 1246 open bugs. In addition, we closed 194 pull requests.
As in previous years, we used the live tracker from Benjamin Lannon to track our progress: Given the focus on shipping vscode.dev , not everybody on the team had cycles for clean-up, so some issue clean-up will continue in November. After housekeeping, we also addressed feature requests and community pull requests . Watch a highlight of the new features in this version in the VS Code team's release party. You can find the recording of the event on our YouTube channel.
Visual Studio Code for the Web - vscode.dev (Preview) This iteration, we released a preview of Visual Studio Code for the Web. Visual Studio Code for the Web provides a zero-install experience running entirely in your browser, allowing you to quickly and safely browse source code repositories and make lightweight code changes. To get started, go to https://vscode.dev in your browser. VS Code for the Web has many of the features of VS Code desktop that you love, including search and syntax highlighting, along with extension support to work on your codebase.
In addition to opening repositories, forks, and pull requests from source control providers like GitHub and Azure Repos, you can also work with code that is stored on your local machine. Not all extensions can run when VS Code is in the browser. Extensions that are purely declarative, such as themes, snippets, or grammars, can run unmodified in the browser. However, extensions that need to run code must be updated by the extension authors.
We'd like to say thank you to the extension authors that already have published their extensions as web extensions . You can learn more about https://vscode.dev in our blog post , documentation , and live stream . Workbench Settings editor accessibility We made various Settings editor accessibility improvements: The Settings editor scrolls back to the top after performing a search, so the user does not end up midway through the search results after each search.
The settings scope switcher is accessible via keyboard. Deprecated setting text blocks display an icon. Previously, the deprecated text was distinguished from the rest of the setting text only by color. More UI elements within the Settings editor have the setting ID as their name. Updated search icons The search icons are now the same weight and the match whole word icon was updated to be more distinguishable from the rest.
Parameter hint highlight VS Code now highlights the current parameter in the parameter hint and the color can be themed via editorHoverWidget.highlightForeground . Editor Improved bracket pair guides We continued iterating on bracket pair guides. Horizontal lines now outline the scope of a bracket pair. Also, vertical lines now depend on the indentation of the code that is surrounded by the bracket pair. Bracket pair guides can be enabled by setting editor.guides.bracketPairs to true (defaults to false ).
We added a third option " active " to only show a bracket pair guide for the active bracket pair. The new setting editor.guides.bracketPairsHorizontal controls if and when to render horizontal guides (defaults to active ). New themable colors editorBracketPairGuide.background{1,...,6} and editorBracketPairGuide.activeBackground{1,...,6} can be used to customize the color of bracket pair guides. Customizable bracket pairs You can now configure bracket pairs for a specific programming language through settings. editor.language.brackets can be used to configure which bracket characters should be matched .
If set, editor.language.colorizedBracketPairs independently configures which bracket pairs are colorized when bracket pair colorization or bracket pair guides are enabled. "[javascript]" : { "editor.language.brackets" : [ [ "[" , "]" ], [ "(" , ")" ] ], "editor.language.colorizedBracketPairs" : [ [ "[" , "]" ] ] }, Display hovers above or below the current line You can now choose between displaying IntelliSense hovers above (default) or below the current line.
By setting editor.hover.above to false , hovers will render below the current line. Unicode directional formatting characters To address CVE-2021-42574 , VS Code now renders Unicode directional formatting characters by default. Consider the following text snippet: // from, to, amount transferBalance ( 5678 , 6776 , 4321 , "USD" ); The above text snippet contains two explicit directional formatting characters, U+202E ( RIGHT-TO-LEFT OVERRIDE ) and U+202C ( POP DIRECTIONAL FORMATTING ).
These characters can influence Unicode's Bidirectional Algorithm and could be used to craft source code that renders differently than what compilers would execute. The special rendering of these directional formatting characters can be turned off by setting editor.renderControlCharacters to false . The setting editor.renderControlCharacters is now true by default. Extensions Verified extension publishers VS Code now shows if the domains of an extension publisher are verified by the Visual Studio Marketplace.
Theme: GitHub Light Theme If you are an extension author, more details about how to become a verified publisher can be found in the Publishing Extensions topic. Terminal New default keybindings for special characters The following keybindings were added that are typically supported in other terminals: ctrl+shift+2 : Inputs the null character ( 0x00 ). ctrl+shift+6 : Inputs the record separator character ( 0x1E ). ctrl+/ : Inputs the unit separator character ( 0x1F ).
Languages Configure how HTML completes attributes There is a new setting html.completion.attributeDefaultValue that lets you choose how values are filled in when an HTML attribute is completed: doublequotes : The value is placed in double quotes (default) singlequotes : The value is placed in single quotes empty : The value is left empty Emmet improvements The new Emmet: Update Tag command ( editor.emmet.action.updateTag ) updates the placeholder with the HTML tag to be updated.
The extension also activates now when one tries to run any Emmet command. This change should fix an issue where some commands were not found when run from the Command Palette, while also keeping the activation event list more precise so that Emmet does not start up unnecessarily, such as in an empty workspace. For multi-root workspaces, Emmet now sources snippets from all workspace folders, rather than just the first one.
As a result, custom snippets from all workspace folders will be suggested when editing an applicable file in the workspace. Notebooks Find and Replace supports capturing groups The Find and Replace widget in the notebook editor now supports regular expression capturing groups. In the short video below, replace uses the first (and only) captured text ('a'). Better selection of output renderers and mimetypes Notebook cells can output multiple types of data (mimetypes) that can be rendered in different ways both by VS Code itself and extensions.
Previously, VS Code had basic memoization (caching) of the selected renderer for a mimetype, and you could manually configure your preferred mimetypes us
The rest of this page is on the live site.