February 2019 (version 1.32)

Updates: Issues addressed in each update - 1.32.3 - 1.32.2 - 1.32.1

Downloads: Windows: User System | Mac | Linux 64-bit: deb rpm tarball | 32-bit: deb rpm tarball

Welcome to the February 2019 release of Visual Studio Code. There are a number of significant updates in this version that we hope you will like, some of the key highlights include:

If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

You can also check out this 1.32 release highlights video from Cloud 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 - Keyboard navigation control, Outline view and breadcrumbs use tree widget.

- Keyboard navigation control, Outline view and breadcrumbs use tree widget. Editor - Fix All Source Action allows you to fix on save, improved column selection.

- Fix All Source Action allows you to fix on save, improved column selection. Languages - No reload required when installing TypeScript and Markdown extensions.

- No reload required when installing TypeScript and Markdown extensions. Extension Authoring - Add commands to the Debug toolbar, track last method signature choice.

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

Preview and apply new themes

You can now preview and apply color and file icon themes immediately after installing an extension that contributes them.

Keyboard Shortcuts editor

You can now edit the when clause of a keybinding in the Keyboard Shortcuts editor.

We removed the link that opens your keybindings.json file from the Keyboard Shortcuts editor in favor of the {} button on the right of the editor title bar.

When directly editing your keybindings.json file, the default keybindings are no longer shown on the left. If you prefer to see Default Keybindings, you can check the Workbench > Settings: Open Default Keybindings setting ( workbench.settings.openDefaultKeybindings to true ).

Automatic Keyboard Navigation setting

A new setting List: Automatic Keyboard Navigation controls whether lists and trees capture lexicographic keypresses in order to navigate and filter elements. If disabled, keyboard navigation becomes modal and the list.toggleKeyboardNavigation command will toggle its state. You can assign a specific keyboard shortcut to that command. For example, you could set it to be / and only after pressing / , will subsequent keypresses filter items in lists/trees. This setting defaults to enabled.

Below is the keybinding to toggle keyboard navigation with / for the File Explorer:

{ "key" : "/" , "command" : "list.toggleKeyboardNavigation" , "when" : "filesExplorerFocus" }

Default title bar style on Linux

After listening to user feedback, we have made the decision to revert our change of the default setting window.titleBarStyle from custom back to native on Linux. We still recommend the custom title bar for those needing better accessibility support. More information on this change has been documented in our Linux setup page.

The Outline document symbol view and breadcrumb picker have adopted the new tree widget. The new implementation makes them faster and gives better filtering support, along with other new tree widget enhancements.

Editor

Hover and Problems peek improvements

In this release, a command bar with Quick Fix and Peek Problem actions was added to the Problems hover. The Quick Fix action applies Quick Fixes from the hover and the Peek Problem action will open the peek view in the editor.

From a Problems peek view, you can now navigate to the previous and next error/warning.

We also improved the appearance of the hovers and the Problems peek view. Hovers with problems and code blocks are given enough space to show their contents:

Auto fix and preferred Code Actions

The Code Action API powers VS Code's Quick Fixes (the lightbulbs you see in the editor). Although there may be many Quick Fixes for a given error, there is often one that is the most reasonable fix for the problem. For example, fixing a spelling error is usually the more likely fix than generating new fields.

Extensions can now mark a Code Action as "preferred" to indicate that it is the most reasonable fix for the underlying problem. When a preferred fix is available, a blue badge is added to the lightbulb. Preferred fixes can be automatically applied using the Auto Fix command (⌥⌘. (Windows, Linux Shift+Alt+.)).

Preferred Quick Fixes should generally:

Correctly fix the underlying error (and not suppress it).

Be a reasonable fix for the error.

Not perform extensive operations unexpectedly.

Refactoring Code Actions can also be marked as preferred to indicate that they are the most reasonable refactoring. For example, while multiple Extract constant refactorings may be available, the user usually wants to extract to the nearest local. If that refactoring Code Action is marked isPreferred , users can set up a single keybinding for it:

{ "key" : "ctrl+shift+r ctrl+e" , "command" : "editor.action.codeAction" , "args" : { "kind" : "refactor.extract.constant" , "preferred" : true } }

Fix All Source Actions

The new source.fixAll CodeActionKind establishes a convention for extensions that can auto fix errors in a file. This new Source Action kind is similar to Organize imports and makes it easy to configure keybindings for fix all actions or enable auto fix on save:

// On save, run both fixAll and organizeImports source actions "editor.codeActionsOnSave" : { "source.fixAll" : true , "source.organizeImports" : true , }

The TSLint extension already uses source.fixAll Code Action kind to implement fix all and auto fix on save.

Default keybinding change for expandLineSelection

The command expandLineSelection is now bound by default to Ctrl+L ( Cmd+L on macOS) and not to Ctrl+I ( Cmd+I ).

Improved column selection

With the Multi Cursor Modifier setting configured to use Ctrl ( Cmd on macOS) "editor.multiCursorModifier": "ctrlCmd" , and thus the Alt modifier is only used for Go to Definition, it is now possible to press the Alt modifier when dragging a selection in the editor to toggle between a regular selection or a column selection.

In the following video, the selection begins as a regular selection and then Alt is pressed and held until the mouse button is released:

Languages

TypeScript 3.3.3

This release includes TypeScript 3.3.3, a small update that fixes a few important bugs.

No reload required when installing TypeScript extensions

Last iteration, VS Code was changed to no longer require a reload after installing the vast majority of extensions. VS Code now also supports dynamic loading of TypeScript plugin extensions as well. When you install a new TypeScript extension, such as TSLint, the extension is automatically enabled without requiring a reload.

No reload required when installing Markdown extensions

In addition, you no longer need to reload VS Code after installing an extension such as GitHub Markdown Preview. Any active Markdown previews will be automatically updated as soon as a Markdown extension is installed.

Improved HTML IntelliSense for ARIA attributes

Thanks to data retrieved from W3C and MDN, VS Code now shows descriptions for ARIA (Accessible Rich Internet Applications) attributes and DOM events.

Removed Razor support in HTML extension

The legacy ASP.NET Razor support has been removed. We now recommend the C# extension for editing Razor files.

Debugging

Font configuration for Debug Console

Now it is possible to configure the font size, font family, and line height in the Debug Console using these settings: debug.console.fontSize , debug.console.fontFamily , and debug.console.lineHeight .

Debug Console text wrapping

Thanks to the new tree widget adoption, the debug console now supports automatic text wrapping for all its elements, even attributes inside objects.

Integrated Terminal

Variable support in send sequence command

It's now possible to use variables with the workbench.action.terminal.sendSequence command, for example:

{ "key" : "ctrl+shift+t" , "command" : "workbench.action.terminal.sendSequence" , "args" : { "text" : ". ${file}" } }

Preview features

Preview features are not ready for release but are functional enough to use. We welcome your early feedback while they are under development.

Automatically open a URI when debugging a server program

Developing a web program typically requires opening a specific URL in a web browser in order to hit the server code in the debugger. In this milestone, we added a first cut of a new VS Code feature that tries to automate this process in a flexible way.

Here is an example of a simple Node.js Express application:

var express = require ( 'express' ); var app = express (); app . get ( '/' , function ( req , res ) { res . send ( 'Hello World!' ); }); app . listen ( 3000 , function () { console . log ( 'Example app listening on port 3000!' ); });

This application first installs a "Hello World" handler for the "/" URL and then starts to listen for HTTP connections on port 3000. The port is announced in the Debug Console and typically the developer would now type http://localhost:3000 into their browser application.

The new feature makes it possible to add a structured property serverReadyAction to any launch config and select an "action" to be performed:

{ "type" : "node" , "request" : "launch" , "name" : "Launch Program" , "program" : "${workspaceFolder}/app.js" , "serverReadyAction" : { "pattern" : "listening on port ([0-9]+)" , "uriFormat" : "http://localhost:%s" , "action" : "openExternally" } }

Here the pattern property describes the regular expression for matching the program's output string that announces the port. The pattern for the port number is put into parenthesis so that it is available as a regular expression capture group. In this example, we are extracting only the port number, but it is also possible to extract a full URI.

The uriFormat property describes how the port number is turned into a URI. The first %s is substituted by the first capture group of the matching pattern.

The resulting URI is then opened outside of VS Code ("externally") with the standard application configured for the URI's scheme.

Alternatively, the action can be set to debugWithChrome . In this case, VS Code starts a Chrome debug session for the URI (which requires that the Debugger for Chrome extension is installed). In this mode, a webRoot property can be added that is passed to the Chrome debug session.

To simplify things a bit, most properties are optional and we use the following fallback values:

pattern : "listening on.* (https?://\\S+|[0-9]+)" which matches the commonly used messages "listening on port 3000" or "Now listening on: https://localhost:5001".

: which matches the commonly used messages "listening on port 3000" or "Now listening on: https://localhost:5001". uriFormat : "http://localhost:%s"

: webRoot: "${workspaceFolder}"

And here the feature in action:

Please note that in the preview release of the feature:

The pattern is only matched in the Debug Console. It doesn't yet work if the debug target is launched in the Integrated Terminal (and it will never work in external terminals).

The feature does not warn if debugWithChrome is configured but the Debugger for Chrome extension is not installed.

is configured but the extension is not installed. It is not yet possible to use other browser-based debuggers.

Extension Authoring

Contributing commands to debug toolbar

Now extensions can contribute commands to the debug toolbar.

Here's an example from an extension's package.json :

"contributes" : { "commands" : [ { "command" : "dart.hotReload" , "title" : "Hot Reload" , "icon" : { "dark" : "./media/hot_reload_inverse.svg" , "light" : "./media/hot_reload.svg" } } ], "menus" : { "debug/toolbar" : [ { "command" : "dart.hotReload" , "when" : "debugType == dart" , "group" : "dart" } ] } }

The extension adds a "Hot Reload" button seen on the right of the debug toolbar.

SignatureHelpContext.activeSignatureHelp

SignatureHelpContext object now have an activeSignatureHelp field that tracks the previously active signature:

import * as vscode from 'vscode' ; class MySignatureHelpProvider implements vscode . SignatureHelpProvider { provideSignatureHelp ( document : vscode . TextDocument , position : vscode . Position , token : vscode . CancellationToken , context : vscode . SignatureHelpContext ): vscode . ProviderResult < vscode . SignatureHelp > { // The active signature help when this provider was triggered or undefined if // no signature help was active. console . log ( context . activeSignatureHelp ); ... } }

Providers can use this to track which overload was selected by the user before the signature help provider was retriggered.

Proposed extension APIs

Every milestone comes with new proposed APIs and extension authors can try them out. As always we are keen on your feedback. This is what you have to do to try out a proposed API:

You must use Insiders because proposed APIs change frequently.

You must have this line in the package.json file of your extension: "enableProposedApi": true .

file of your extension: . Copy the latest version of the vscode.proposed.d.ts file into your project.

Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.

workspace.registerResourceLabelFormatter

export interface ResourceLabelFormatter { scheme : string ; authority ?: string ; formatting : ResourceLabelFormatting ; } export interface ResourceLabelFormatting { label : string ; // myLabel:/${path} separator : '/' | ' \\ ' | '' ; tildify ?: boolean ; normalizeDriveLetter ?: boolean ; workspaceSuffix ?: string ; authorityPrefix ?: string ; } export namespace workspace { export function registerResourceLabelFormatter ( formatter : ResourceLabelFormatter ): Disposable ; }

Extensions can use the registerResourceLabelFormatter to contribute dynamically resource label formatters that specify how to display URIs everywhere in the workbench.

Engineering

Linux 32-bit support ends soon

VS Code is using Electron as framework to run on multiple platforms. We are currently using Electron version 3.x, which will be the last version to support Linux on 32-bit architectures. As we are planning to move to Electron 4.x soon (1-2 months), this means that VS Code will no longer run on Linux 32-bit. Please update your version of VS Code to the 64-bit version. All your settings and extensions will work as before without the need to migrate anything. You can read the related blog post from Electron for more information.

Strict null progress

We continued to make good progress towards strict null checking the main VS Code codebase. This iteration, we cut the number of remaining strict null errors in half, fixing over 2000 errors. We still have around 1800 strict null errors left, and many of the remaining errors are tricky ones, but the end is in sight.

Compiling to ES6

VS Code is written TypeScript, and TypeScript is compiled into JavaScript. TypeScript can target different JavaScript versions and with this release, we target ES6 JavaScript. ES6 is much closer to TypeScript and produces less code, which means faster loading times.

Note: This means our JavaScript output uses classes as defined in JavaScript. We have a utility in place that still allows functions to "extend" from those classes and we have created a tracking item for extensions authors to now emit ES6 as well. Everything should still work as before but we encourage everyone to get on the ES6 train.

Contributions to Extensions

GitHub Pull Requests

This milestone we continued working on improvements to the GitHub Pull Requests extension.

Below are some of the new features:

View and assign reviewers and labels on the pull request description page.

GitHub Pull Request tree views now show in its own view container. You can also choose to show them in Source Control view by modifying githubPullRequests.showInSCM .

. View and modify reactions on comments.

Vetur

The Vetur extension now provides IntelliSense (smart completions) for Vue.js interpolations.

The completion items are sourced from Vue.js props , data , computed , and methods API calls. The source code, along with any JSDoc documentation, are used as completion item descriptions.

When using child components from parent components, Vetur also offers IntelliSense on the child component's props .

Other notable features include:

Using Prettier as an option for <template> formatter.

formatter. GraphQL custom block syntax highlighting.

Pug interpolation syntax highlighting.

You can learn more about the features in Vetur's Changelog.

New documentation

Bundling extensions with webpack

For extension authors, there is a new Bundling Extensions topic on bundling extensions files with webpack to reduce extension load time.

Working with JavaScript

A new Working with JavaScript article describes advanced JavaScript features supported by VS Code. You'll learn the benefits of adding JavaScript project files (jsconfig.json) to your code as well as how to enable type checking.

Notable fixes

55084: Allow to create/open file names containing backslash

68204: New file doesn't show in explorer after creating from path like 'folder/subfolder/file.txt'

68316: New workbench explorer treeview fails to update properly

68616: Debug points getting hit but no visual indication when debugging nodejs (mocha tests)

68691: No input box to create new file in Explorer

68627: 'Reveal in sidebar` does not work

67970: New explorer: switching editors should clear focus

This release also include a security update for Microsoft Security Response Center CVE-2019-5786, which you can read about in this Electron blog post.

Thank you

Last but certainly not least, a big Thank You! to the following folks that helped to make VS Code even better:

Contributions to our issue tracking. Please see our Community Issue Tracking page, if you want to help us manage incoming issues:

Contributions to vscode :

Contributions to vscode-languageserver-node :

Contributions to node-jsonc-parser :

John Spurlock (@johnspurlock): Fix a few typos in doc comments PR #15

Contributions to vscode-generator-code :

Contributions to vscode-vsce :

小胡子哥 (@barretlee): Fixbug: increase the stdout/stderr buffer of exec PR #309

Contributions to vscode-recipes :

Contributions to localization :

There are over 700 Cloud + AI Localization community members using the Microsoft Localization Community Platform (MLCP), with over about 100 active contributors to Visual Studio Code.

We appreciate your contributions, either by providing new translations, voting on translations, or suggesting process improvements.

Here is a snapshot of contributors. For details about the project including the contributor name list, visit the project site at https://aka.ms/vscodeloc.