May 2022 (version 1.68)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. May 2022 (version 1.68) Update 1.68.1 : The update addresses these issues . Downloads for 1.68.1 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the May 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: Configure Display Language - See installed and available Language Packs in their language.
Problems panel table view - View errors and warnings as a table to quickly filter on their source. Deprecated extensions - Learn whether an extension is deprecated or should be replaced. Extension sponsorship - Support the developers who build your favorite extensions. Hide Explorer files using .gitignore - Reuse your existing .gitignore to hide files in the Explorer. Terminal color and contrast enhancements - Find match background color, min contrast ratio.
Git branch protection - Branch protection available right inside VS Code. TypeScript Go to Source Definition - Jump directly to a symbol's JavaScript implementation. VS Code for the Web localization - vscode.dev now matches your chosen browser language. Development Container specification - Learn more about the evolving dev container spec. Preview: Markdown link validation - Detects broken links to headers, images, and files.
If you'd like to read these release notes online, go to Updates on code.visualstudio.com . 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. Workbench Configure Display Language improvements The Configure Display Language command has been refreshed to include: The name of the language in that language. An Available languages section that shows what languages aren't installed on your machine and selecting one will automatically install it and apply that language.
Theme: Panda Theme This should help with the discovery of available Language Packs . Please let us know what you think! Problems panel table view This milestone we added a new capability for users to toggle the view mode of the Problems panel between a tree and a table. Compared to the tree view, the table surfaces the source (language service or extension) of each problem, which allows users to filter the problems by their source.
Theme: GitHub Dark Dimmed Theme You can toggle the view UI with the View as Table/View as Tree button in the upper right of the Problems panel or change the default view mode with the Problems: Default View Mode setting ( problems.defaultViewMode ) Deprecated extensions In this milestone, we have added support for deprecated extensions in VS Code. An extension can be simply deprecated or deprecated in favor of another extension or when its functionality is built into VS Code.
VS Code will render extensions as deprecated in the Extensions view, as shown below. A deprecated extension that is no longer being maintained. An extension deprecated in favor of another extension. In this case, VS Code does not allow users to install this extension. A deprecated extension with its functionality built-in to VS Code that can be enabled by configuring settings. VS Code will not automatically migrate or uninstall a deprecated extension.
There will be a Migrate button to guide you to switch over to the recommended extension. Theme: GitHub Dark Dimmed Theme Note: The list of deprecated extensions is maintained by the VS Code. If you have an extension that you believe should be deprecated, reach out to us by commenting in this discussion . Sponsoring extensions VS Code now allow users to sponsor their favorite extensions. When an extension can be sponsored, VS Code will render a Sponsor button in the Extensions view Details page like below: Theme: GitHub Dark Dimmed Theme The Sponsor button will direct you to the extension's sponsorship URL, where you can provide your support.
Refer to Extension sponsorship to learn how to opt into this feature for your extension. Hide files in Explorer based on .gitignore The File Explorer now supports parsing and hiding files that are excluded by your .gitignore file. This can be enabled via the Explorer: Exclude Git Ignore ( explorer.excludeGitIgnore ) setting. This setting works alongside files.exclude to hide unwanted files from the Explorer. Note : At this time, negated globs such as !package.json are not parseable.
Lock hover position Some custom hovers are difficult or impossible to mouse over due to the presence of other UI elements (for example, a scroll bar). Holding Alt while a hover is active will now "lock" it, giving it a wider border and preventing mouse movement outside of the hover from hiding it. This is primarily an accessibility feature to make hovers play nicely with screen magnifiers but it is also useful for copying text from hovers.
Note that this feature only applies outside of the editor because editor hovers can always be moused over unless specified otherwise via the editor.hover.sticky setting. Settings editor improvements The Settings editor now shows a default value override indicator for language-specific settings. You can view language-specific settings by adding a language filter in the Settings editor search bar, either by typing it out explicitly ( @lang:javascript ), or by clicking the filter button on the right of the search bar, and selecting the Language option.
When the default value override indicator shows up, it indicates that the default value of the language-specific setting has been overridden by an extension. The indicator also indicates which extension overrode the default value. Theme: Light Pink This iteration also fixes a behavior where some links in the Settings editor were not redirecting properly when there was already a search query in the Settings editor search bar.
The links also now have proper styling so that it is clearer when one is hovering over them. <video src="/assets/updates/1_68/settings-editor-working-links.mp4" autoplay loop controls muted title="After searching for the word "font" in the Settings editor, and selecting the terminal category in the table of contents, the setting terminal.integrated.fontFamily shows up, and its description contains a link to the editor.fontFamily setting.
Clicking on the link now brings you correctly to the setting."> Theme: Light Pink Comments widget primary button The comments widget uses the primary button color for the first (rightmost) action: Terminal Find match background color Last release find in the terminal was implemented to show a border around all matches, but this was a temporary solution until support for changing the background of cells dynamically was possible.
A colored background is now the default for themes when highlighting matches and the overall experience should look similar to the editor. If you're a theme author that adopted terminal.findMatchBorder or terminal.findMatchHighlightBorder , we recommend migrating to terminal.findMatchBackground and terminal.findMatchHighlightBackground if that would fit the theme better or help contrast. Improvements to contrast and the minimum contrast ratio The find match background work added a lot more flexibility in how the terminal works with background and foreground colors.
Because of this, improvements were made around contrast in the terminal, aligning the terminal visuals closer to the editor. In addition, there is now the minimum contrast ratio feature that changes the foreground of text dynamically to help with visibility. Luminance will now go in the other direction if contrast isn't met. For example, if contrast isn't met for dark grey text on a lighter grey background with pure black (#_000000), the color will also try to move towards white and the value that best meets the desired contrast ratio will be used.
Selection is now drawn below the
The rest of this page is on the live site.