Text of code.visualstudio.com › updates › v1_67 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

April 2022 (version 1.67)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. April 2022 (version 1.67) Update 1.67.1 : The update addresses this security issue . Update 1.67.2 : The update addresses these issues . Downloads for 1.67.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the April 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: Explorer file nesting - Nest generated files under source files in the Explorer. Settings editor filters - Filter button brings up searches such as @Modified settings Bracket pair colorization - Colored bracket pairs are now enabled by default. Toggle inlay hints - Ctrl+Alt to quickly hide or show inlay hints in the editor.

Drag and drop to create Markdown links - Drop files into the editor to create Markdown links. Find All References in Markdown - Quickly find all references to headers, files, URLs. Java extension updates - Now supporting inlay hints and lazy variable resolution. UX Guidelines for extension authors - Guidance for VS Code extension UI best practices. New Rust language topic - Learn how to use the Rust programming language 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 April 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. Workbench Explorer file nesting The Explorer now supports nesting related files based on their names. There are several settings to control this behavior: explorer.fileNesting.enabled - Controls whether file nesting is enabled at-large. It can be set either globally or for a specific workspace. explorer.fileNesting.expand - Controls whether nested files are expanded by default. explorer.fileNesting.patterns - Controls how files are nested.

The default configuration provides nesting intelligence for TypeScript and JavaScript projects, but you're encouraged to modify this to fit your own project's structure. Some examples: Default configuration: Nesting under index.ts when a file matches the directory's name ( "index.ts": "${dirname}.ts" ): Nesting files that have the same name as a different file but with an added segment ( "*": "${basename}.*.${extname}" ): Theme: GitHub Light High Contrast File nesting has been available through an experimental setting for several iterations.

The behavior now is mostly unchanged, except for file operations. The experimental setting explorer.experimental.fileNesting.operateAsGroup has been removed in favor of treating nests as a group when collapsed, but as single entities otherwise. This means that if you want to copy, cut, drag, or delete an entire nested stack of files, you can collapse the nest then operate on it as a single entity. When nested elements are expanded, selections will behave as normal.

Settings editor search filter button The Settings editor search control now contains a funnel button on the right side. Clicking on the button shows a list of filters that you can apply to the search query in order to filter down the results. Theme: Light Pink Settings editor language filter indicator Settings editor language filters now change the scope text to more clearly show which language is being acted on when a language filter is applied.

The short video above shows the Markdown language filter ( @lang:markdown ) being applied to the filtered settings. For reference, when a language filter is applied, modifying a setting's value will modify the value of that setting for that language only. Language-specific settings are scoped in settings.json by the language identifier : "[markdown]" : { "editor.wordBasedSuggestions" : "off" } Save files after refactoring Refactorings, like Rename, often modify multiple files and leave them with unsaved changes (dirty).

External development tools usually require these files to be saved. To make this workflow easier, there is a new setting files.refactoring.autoSave that defaults to true and controls if files that were part of a refactoring should be saved automatically. Exclude dirty editors in editor limit A new setting workbench.editor.limit.excludeDirty controls if the maximum number of opened editors should exclude dirty editors for counting towards the configured limit.

The setting is disabled by default ( false ). Bring back "Uncommitted Changes" to Timeline When we introduced Local History feature last month, we removed the Uncommitted Changes entry from the Git timeline provider because it felt a bit redundant. However, some users see real value in this timeline entry and now you can bring it back by configuring the new git.timeline.showUncommitted setting accordingly. New editor placeholder when opening fails When an editor fails to open, VS Code no longer shows a notification and reveals the previous opened editor.

Instead, there is a generic placeholder with the error message and, in some cases, actions to resolve the error. Language status improvements The language status item now shows formatter conflicts - those happen when multiple formatters for a language are installed but none of them is configured as the default formatter. Also, the language status item is more prominent when containing severe status. Additionally, the language status item will now show hints to switch languages when your document is suspected to be a different language than what is currently set.

This applies only to untitled editors and notebook cells, and can be configured with the workbench.editor.languageDetectionHints setting. Below this is demonstrated in the Handy Dandy Notebook , which supports executing cells in various different languages. Theme: GitHub Light High Contrast Show invalid or incompatible extensions The Extensions view now shows invalid or incompatible extensions in the Installed extension list with error status.

For example, if your VS Code version is 1.67.0-insider and you have installed an extension that requires VS Code version 1.68.0 , then it will show up in the list with incompatible error status. Confirm before quit A new setting window.confirmBeforeClose can be configured to show a confirmation dialog before quitting the application. You can either chose keyboardOnly to bring up the confirmation dialog when a keybinding is used or always , even when using the mouse to quit.

Note : The setting is not entirely new and has been available in VS Code for Web for some time. comments.openView default value The old default value of comments.openView was file , which caused the Comments view to open every time a file with comments was opened. To make the Comments view less noisy, the new default is firstFile , which causes the Comments view to open only the first time a file with comments is opened during a session.

Multiline comments Behind the scenes, VS Code has supported multiline comments since the comments UX was finalized, but multiline comments were never surfaced in the UI. You can now see and leave multiline comments. Handle URI in new window Whenever a VS Code URI contains a query parameter windowId=_blank , VS Code will handle it in a new window. Example: vscode://vscode.git/clone?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode-vsce.git&windowId=_blank .

Editor Bracket pair colorization enabled by default Given the positive feedback of the new bracket pair colorization feature introduced in the 1.60 release , we enabled bracket pair colorization by default. Bracket pair colorization can be disabled by setting "editor.bracketPairColorization.enabled" to false . B

The rest of this page is on the live site.