VS Code 1.74 has been released. This version mainly brings the following optimizations:

Some functions are introduced below:

Automatic display logic of custom resource manager

This release introduces a new setting explorer.autoRevealExclude, which allows you to configure which files are automatically shown in Explorer if auto-reveal is enabled (explorer.autoReveal, defaults to true).

The autoRevealExclude setting uses glob patterns to exclude files, similar to files.exclude, and also supports sibling matching through when clauses.

The default excludes node and bower modules:

  "explorer.autoRevealExclude": {
    "**/node_modules": true,
    "**/bower_components": true

Set editor indicators, hover and links to be keyboard navigable

Indicators, hovers, and links in the settings editor are now keyboard navigable, and the styling of some links has been tweaked for better consistency across the settings editor.Set editor indicator hover to behave better in terms of tab stops and maintaining keyboard focus.

This improvement is still experimental and currently only enabled for settings editor indicator hovers, not all hovers in VS Code.

Use the keyboard to navigate settings in the settings editor and modify indicators elsewhere

Hide the badge of the view container

Similar to how view containers are hidden by right-clicking on them, it is now also possible to hide badges on containers (displayed in activity bars, panels, and sidebars).

Badges typically display a number, icon, or progress indicator for a particular view container, for example, the number of pending changes for a source control view.

Manage insecure Git repositories

VS Code uses git.exe for all Git operations. Starting with Git 2.35.2, users cannot run Git operations on repositories in folders that are not owned by the current user, because the repository is considered potentially insecure.

Starting with this release, VS Code will display a welcome view in the source control view along with an error notification if you try to open such a potentially unsafe repository. Both the welcome view and notifications come with a “Manage Unsafe Repositories” command, which allows you to view a list of potentially unsafe repositories, manually mark them as safe before opening them.

The manage unsafe repository command is also available in the command palette, marking a repository as safe will add the repository location to the safe.directory git configuration.

Terminal quick fix improvements

Terminal quickfixes are now displayed in the code manipulation controls to align with the in-editor experience.

Trigger the quickfix in Terminal and show a menu with a play button to the left of the action label

remote tunnel

Remote Tunnels, now available as a preview feature for the stable release of VS Code, allows you to securely access your machine and VS Code from any device, anywhere.

To enable remote tunnel access, you can:

  • From the account menu or the command palette chooseOpen remote tunnel access.
  • From a computer that has VS Code installed and is on the PATH run code tunnel.
  • Download the new VS Code CLI, and run./code tunnel.

After opening tunnel access, you can use vscode.dev to connect to your computer from any device, or use the Remote – Tunnels extension in the VS Code desktop.

To learn more, check out the feature’s blog post or the remote tunneling documentation.

JavaScript debugging

Support console.profile

The JavaScript debugger now supports console.profile. When run under a debugger, this function will collect CPU profiles for code between console.profile() and console.profileEnd().


The generated .cpuprofile file will be saved in your workspace folder and can be opened and viewed using VS Code’s built-in profile viewer.

Support for nested source maps

Sometimes, especially in a monorepo setup, the source code may be compiled once, then recompiled or bundled again. In many cases, this problem causes the source maps of the generated package to reference the compiled files created in the first step.

The JavaScript debugger now automatically recursively parses source maps, allowing you to debug original source files without additional steps.

TypeScript 4.9

VS Code now ships with TypeScript 4.9, bringing new TypeScript language features such assatisfiesoperators and automatic accessors. On the tools side, file monitoring has been improved and many other fixes and improvements have been made.

Check out the TypeScript 4.9 announcement for more information on this update.

Go to Definition on return

JavaScript and TypeScript now support running Go to Definition on the return keyword to quickly jump to the top of the returned function, useful when dealing with long, complex or highly nested functions.

You can use the Go to Definition command/keybinding (F12) or simply use Cmd/Alt + click the return keyword.

Remote development extension

The Remote Development extension allows the use of containers, remote machines, or the Windows Subsystem for Linux (WSL) as a fully functional development environment. Highlights of this release include:

  • Dev container GPU support
  • Development container Cygwin/Git Bash socket forwarding
  • Remote Tunnel Extension – Connect to remote computers without SSH.

Learn about new extensions and bug fixes in the Remote Development release notes.

More features can be read in the release announcement.

#Visual #Studio #Code #released #introducing #remote #tunnel #function #News Fast Delivery

Leave a Comment

Your email address will not be published. Required fields are marked *