November 2022 (version 1.74)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. November 2022 (version 1.74) Update 1.74.1 : The update addresses these issues . Update 1.74.2 : The update addresses these issues . Update 1.74.3 : The update addresses this security issue . Downloads for 1.74.3 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the November 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: Customize Explorer auto reveal - Decide which files scroll into view in the Explorer. Hide Activity bar and Panel badges - Simplify the editor UI by toggling state badges. Audio cues for notebooks and diff view - Sounds for cell run results, added or removed lines. Merge editor Undo/Redo - Quickly revert or reapply merge conflict actions.
Manage unsafe repositories - Prevent Git operations on folders not owned by you. JavaScript console.profile collection - Easily create CPU profiles for viewing in VS Code. Go to Definition from return - Jump to the top of JavaScript/TypeScript functions. Remote Tunnels - Create a connection to any machine, without needing SSH. Jupyter notebook "Just My Code" debugging - Avoid stepping into Python library code. Dev Container GPU support - Request a GPU when creating a Dev Container.
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. Accessibility Audio cues for notebook execution There are now audio cues for when notebook cells finish running. The cue is different to indicate whether the cell ran successfully or failed.
Audio cues for diff review mode In a diff editor, when Go to Next Difference is triggered, a specific audio cue will play to indicate whether the cursor is on an inserted or deleted line. If you are curious about the available audio cues, you can hear them via the Help: List Audio Cues dropdown. Keyboard-navigable Settings editor indicators, hovers, and links The indicators, hovers, and links in the Settings editor are now navigable by keyboard.
The styling of some of the links have also been adjusted for better consistency across the Settings editor. Settings editor indicator hovers now behave much better when it comes to tabstops and maintaining keyboard focus. This improved behavior is still experimental, and is currently only enabled for the Settings editor indicator hovers, rather than for all hovers across VS Code. Theme: Light Pink (preview on vscode.dev ) Workbench Custom Explorer autoreveal logic The highly upvoted issue #87956 ("Allow to set explorer.autoReveal per specific folder") has been fixed by the introduction of a new setting explorer.autoRevealExclude .
This setting lets you configure which files get autorevealed in the Explorer if the autorevealing is enabled ( explorer.autoReveal , default true ). The autoRevealExclude setting uses glob patterns for excluding files and similar to files.exclude , also supports sibling matching via when clauses. The default value excludes node and bower modules: { "explorer.autoRevealExclude" : { "**/node_modules" : true , "**/bower_components" : true } } Hide badges per view container Similar to how you were able to hide view containers by right-clicking the view container, you can now hide the badge on the container (displayed in the Activity bar, Panel, and Secondary Side bar).
Badges often display a number, icon, or progress indicator for a specific view container, for example, the number of pending changes for the Source Control view. Merge Editor This release ships some improvements and bug-fixes for the merge editor. Highlights include: Undo/Redo now tracks the handled state of conflicts. Ignore actions in the input views can be used to accept the base version instead of the Mark as handled action in the result view.
Changes that are equal on both sides are now automatically resolved. Extensions that provide git blame functionality now work in the incoming, current, and base editors. Install an extension located on disk You can now install an extension that is located on a local disk drive by using Developer: Install Extension from Location... command. The command will open the platform folder dialog to select the location of the extension's .vsix file.
Editor New word break option for CJK characters A setting called editor.wordBreak can now be used to avoid inserting wrapping points after CJK characters . When configured with keepAll , the wrapping algorithms will try to keep text after CJK characters on the same line. This setting doesn't have any effect on characters from other scripts. New font setting for OpenType fonts Some newer fonts, which support OpenType font variations, support tuning certain axes, like the font weight axis, to achieve font weights that are not configurable via the font-weight CSS property.
In CSS, this is achieved with the font-variation-settings property. If you use such a font, you can now configure editor.fontVariations to true , which will result in VS Code using the "wght" display axis for setting the font weight. If your font supports other axes, it is also possible to configure them directly, for example by setting "editor.fontVariations": "'ital' 0.5" . New indent size setting There is a new setting called editor.indentSize that allows to dissociate the indent size (the number of spaces that make up an indent) from the tab size (the number of spaces that are used to render a Tab character).
This is useful when dealing with files that use mixed tabs and spaces indentations and can be exercised only when using manual indentation configuration. Below is an example configuration: "editor.detectIndentation" : false , "editor.insertSpaces" : true , "editor.tabSize" : 8 , "editor.indentSize" : 2 Command to partially accept inline completions The command Accept Next Word Of Inline Suggestion ( editor.action.inlineSuggest.acceptNextWord ) can be used to accept the next word/non-word segment of the current inline suggestion.
Currently, it can only accept parts of the first line of an inline suggestion. The command is still under development and we are exploring keyboard shortcuts along with alternative splitting rules for future releases. Source Control Manage unsafe Git repositories VS Code uses git.exe for executing all Git operations. Starting with Git 2.35.2 , users are prevented from running Git operations in a repository that is in a folder owned by a user other than the current user, as the repository is deemed to be potentially unsafe.
Starting with this release, if you try to open such a potentially unsafe repository, VS Code will show a welcome view in the Source Control view as well as an error notification. Both the welcome view, and the notification expose the Manage Unsafe Repositories command that lets you review the list of potentially unsafe repositories, mark them as safe, and open them. The Manage Unsafe Repositories command is also available in the Command Palette.
Marking a repository as safe will add the repository location to the safe.directory git configuration . Optimistic user-interface updates After executing a Git operation, a set of git commands (for example, git status ) are executed to update the data model before the Source Control view is updated. There are scenarios in which running these commands can take several seconds to complete (for example, when working with large monorepos), resulting in a delay before the Source Control view is refreshed.
This milestone we have made changes so that the Source Control view is optimistically updated for some of the Git operations (stage, unstage, discard changes, and commit) before git status completes, resulting in a snappier Source Control view. The new capability i
The rest of this page is on the live site.