March 2019 (version 1.33)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. March 2019 (version 1.33) Update 1.33.1 : The update addresses these issues . Downloads for 1.33.1 Windows x64 macOS Intel Linux 64-bit .deb .rpm .tar.gz Snap Linux 32-bit .deb .rpm .tar.gz Welcome to the March 2019 release of Visual Studio Code. There are a number of updates in this version that we hope you will like, some of the key highlights include: Easy Display Language selection - Quick Pick to choose between installed locales.
Configurable IntelliSense display - Filter out elements like keywords or remove displayed icons. Choose default formatter - Set default document formatter by project and language. Go to Definition locations - Open Peek view and/or navigate to primary location. Convert to destructured parameters - New TS refactoring to use named parameter objects. Debugging support for subsessions - See subprocesses displayed under main debug session.
Launch URI with debug session - Automatically open a browser when debugging web server code. Install missing extension dependencies - Detect and offer to install missing dependencies. "Remote Debugging for Node.js" topic - Learn how to attach to Node.js apps running on Azure. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . You can also check out this 1.33 release highlights video from Developer Advocate Brian Clark .
The release notes are arranged in the following sections related to VS Code focus areas. Here are some further updates: Workbench - Improved Source Control view, easier list navigation with screen readers. Integrated Terminal - ConPTY on by default on Windows, rendering performance improvements. Languages - Disable CSS property value completions, TS improved inference and const assertions. Extension Authoring - Finalized smart selection API, install extension command.
Engineering - Official Linux snap package, faster OSS builds with NPM package caching. Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @code ! Workbench Easier Display Language configuration Running the Configure Display Language command will now open a Quick Pick listing the available locales based on the Language Packs you have installed, instead of only opening the locale.json file.
When you make a selection, the locale will be automatically updated and you'll be prompted to restart VS Code for the change to take effect. Improved Source Control view The Source Control view has been aligned to behave like other views, such as the File Explorer, Debug view, etc. Repositories can now be made visible or hidden using context menu actions. Their order and sizing is now preserved. You can also show or hide the Source Control Providers view with context menu actions.
List simple keyboard navigation when screen reader detected When VS Code detects that a screen reader is being used, it automatically turns on simple keyboard navigation for lists. This makes the list keyboard navigation easier for users with a screen reader since each key stroke will navigate to the corresponding item. This behavior applies for all lists and trees in the workbench, for example the File Explorer, Open Editors, and Debug views.
Editor IntelliSense customization There are new settings that control the IntelliSense display: editor.suggest.filteredTypes - Filter specific types from IntelliSense, for instance keywords are filtered with: { "keyword": false } . editor.suggest.maxVisibleSuggestions - Control the number of items IntelliSense shows at once. editor.suggest.showIcons - Enable or disable displaying icons in IntelliSense. Below is an example of TypeScript IntelliSense with keywords filtered out, no icons, and limited to eight suggestions: Default formatter selection Many of our users work on different projects and often different projects use different document formatters.
This has been hard to configure and we have added a new setting to help, editor.defaultFormatter . Now, when there are multiple formatters available, you can define one as the default. In fact, VS Code will encourage you to pick a default formatter. This will update your configuration (as shown below) so that for subsequent save operations, VS Code knows what formatter to pick. We also encourage you to set this value in your project's configuration.
For example, if your project team agrees on a formatter, then it should be spelled out in the project settings file. "[javascript]" : { "editor.defaultFormatter" : "HookyQR.beautify" } Defining a default formatter does not remove alternative formatters. We have added the Format Document With... command, which still allows you to pick a formatter before formatting a document. If needed, you can also reconfigure the default formatter from the dropdown.
Go To Definition customization Some programming languages allow you to define a symbol in multiple locations. This means that a feature like Go to Definition must go to multiple locations at once. VS Code supports this by showing a Peek view with all locations. This behavior can now be fine-tuned with a new setting, editor.gotoLocation.multiple . It can be set to these values: peek - Open Peek view at the current location.
This is the default. gotoAndPeek - Open the primary location (as defined by the extension) and also show a Peek view. goto - Only open the primary location. Snippet variable $WORKSPACE_NAME There is a new snippet variable that resolves to the name of the opened workspace/folder: $WORKSPACE_NAME . Use it as shown in the snippet below: "header" : { "scope" : "javascript,typescript" , "prefix" : "workspace" , "body" : [ "// the ${WORKSPACE_NAME}-project" ], "description" : "Log output to console" } Integrated Terminal ConPTY turned on by default on Windows build 18309+ For supporting versions of Windows 10 Insiders, the new terminal back-end ConPTY will be turned on by default.
This should result in a more stable experience closer to the native terminal and adds 256 color support. If you experience issues, please let us or the Windows Console team know. You can always opt out with this setting: { "terminal.integrated.windowsEnableConpty" : false } Data parsing capped to 12 ms Previously, the amount of data parsed by the terminal was not being capped properly. This meant that on less powerful hardware, the amount of time parsing data and rendering would far exceed the ideal time to render a frame, resulting in laggy UI or a full lock up for commands that generated a lot of output.
There is now a cap in place, which prevents this from exceeding approximately 12 ms, which should avoid these issues. Languages TypeScript 3.4 VS Code now ships with TypeScript 3.4.1 . This update adds support for some new TypeScript language features—such as improved inference and new const assertions—as well as bringing tooling improvements and bug fixes. Convert to destructured parameters refactoring The new Convert to named parameters refactoring for TypeScript lets you quickly organize long function parameter lists by converting the function to take a single named parameter object.
Option to disable CSS property value completion A new setting, css.completion.triggerPropertyValueCompletion , allows you to disable property value completion. For example, if you choose position from p and have this setting set to false , VS Code will not trigger the static | absolute | sticky | ... completions for the property value. This is useful if you would like to use Tab/Shift + Tab to select previous and next completion items.
Debugging Support for subsessions In this milestone, we have added support to display debug sessions as a tree in the debugger UI. Previously debug sessions were displayed as a flat list, which made it difficult to gr
The rest of this page is on the live site.