January 2019 (version 1.31)

Update 1.31.1: The update addresses these issues.

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

Welcome to the January 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.31 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 - Zen Mode hides line numbers, new Screencast mode shows keystrokes.

- Zen Mode hides line numbers, new Screencast mode shows keystrokes. Editor - Smart selection improvements, tune Reference CodeLens location.

- Smart selection improvements, tune Reference CodeLens location. Integrated Terminal - ConPTY support on Windows, Find improvements.

- ConPTY support on Windows, Find improvements. Extension Authoring - Extensions change event, open resource in a browser action.

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!

Extensions

No reload on install

Being able to install extensions without forcing a reload (restart) of VS Code is one of the most upvoted feature requests and we bring it to you in this release. You are no longer required to reload VS Code when you install or enable an extension.

In the example below the user follows the recommendation to install the Vetur extension after opening a .vue file. Notice that the language features provided by the Vetur extension (such as syntax coloring, diagnostic errors) are available immediately after installing the recommended extension.

Reload is also not needed when you uninstall or disable an extension if it is not activated.

Note: There are certain extensions that require reload because of external contributions (contributing to the extension points of other extensions). It requires adoption from the external contribution point owners by listening to the extensions.onDidChange event.

Workbench

New tree widget

We have pushed our widget game to the next level: a new tree widget was created to address performance issues and enable us to provide more features in several workbench areas. The new tree widget was created through composition over our high-performance list widget. We intend to write a separate blog post about this engineering work and the performance improvements. For now, we'll focus on the features instead.

Note: The new tree was adopted in the File Explorer, all Debug trees, Search, and Peek References. The features described below apply to most of those UI areas, unless explicitly disabled by us.

Improved keyboard navigation

There are now three different types of keyboard navigation in trees: simple , highlight , and filter . In both highlight and filter , typing in a tree will display a widget (control) at the top of the tree, which indicates that you are now navigating the tree:

This widget can also be used to switch between the highlight and filter modes. You can configure a keybinding to execute the list.toggleFilterOnType command if you'd like a keyboard shortcut for switching between modes. The Workbench > List: Keyboard Navigation ( workbench.list.keyboardNavigation ) setting sets the default mode, including the simple mode in which typing the first few characters of a tree element simply focuses that element.

Users who have single letter keybindings for list/tree actions can still use this feature by making use of the listAutomaticKeyboardNavigation context key. For example, the VIM extension sets this context key to false to disable automatic keyboard navigation and adds a keybinding / to the list.toggleKeyboardNavigation command, so users can just type / and navigate the tree. Learn more about this in the VSCodeVIM pull request.

Theme authors can customize the widget's colors with the following new theme keys:

listFilterWidget.background

listFilterWidget.outline

listFilterWidget.noMatchesOutline

Note: These keyboard navigation modes currently only work on resolved tree nodes. For example, in the File Explorer, if a folder was never expanded, the tree won't look for its children. We are considering several options to make this experience better.

Hierarchical Select All

Pressing Ctrl+A ( Cmd+A on macOS) in a tree will now expand the tree's selection in a hierarchical fashion.

Customizable indentation

You can now customize the node indentation of all trees across the workbench using the Workbench > Tree: Indent ( workbench.tree.indent ) setting.

Expand/Collapse All

Holding the Alt key while expanding/collapsing tree nodes will now work recursively. Note that recursive expansion only works for nodes previously revealed in the tree. For example, the File Explorer will not automatically expand folders which were never expanded before by the user.

Horizontal scrolling

The Workbench > Tree: Horizontal Scrolling ( workbench.tree.horizontalScrolling ) setting now enables horizontal scrolling on more trees and lists, namely Explorer, Search, SCM, Debug, etc.

Problems panel

Multi-line messages

The Problems panel now shows multi-line diagnostic messages in separate lines. The example below shows how a multi-line error message from TypeScript is now presented.

You can also toggle to show or hide the complete message using either the collapse/expand buttons or the Problems: Show message in single line and Problems: Show message in multiple lines commands.

Trigger Code Actions using a keyboard shortcut

You can now trigger Code Actions from the Problems panel using the same default keyboard shortcut ⌘. (Windows, Linux Ctrl+.) as the Quick Fix command.

Improved the Go menu

We added more navigation actions to the Go menu to make them easier to discover:

Cut command in Explorer context menu

Based on popular request we have added the cut command to the Explorer context menu.

Fast scrolling

Pressing the Alt key enables fast scrolling in the editor and Explorers. By default, fast scrolling uses a 5X speed multiplier but you can control the multiplier with the Editor: Fast Scroll Sensitivity ( editor.fastScrollSensitivity ) setting.

Zen Mode hides line numbers

Turning on Zen Mode will now also hide editor line numbers. This behavior can be controlled via zenMode.hideLineNumbers setting.

Added keyboard navigation in Linux with custom menus

Our custom menus now support the use of the Page Up/Down and Home/End keys to quickly jump to the beginning or end of the menu.

Double-click the application icon to close in Windows/Linux

Due to technical tradeoffs, by default, the custom title bar on Window and Linux removes the functionality of double-clicking the application icon to close the window. The functionality can be regained by enabling the setting window.doubleClickIconToClose with the caveat that you will no longer be able to drag the window from this location or get the system context menu on Windows.

Closing order of editor tabs

A new setting workbench.editor.focusRecentEditorAfterClose allows you to change the order in which editor tabs are closed. By default, tabs will close in most recently used (MRU) order. Changing this setting allows closing tabs from right to left instead.

New title variables

There are three new variables that can be used within the window.title setting:

${activeFolderShort} : The name of the folder the file is contained in.

: The name of the folder the file is contained in. ${activeFolderMedium} : The path of the folder the file is contained in, relative to the workspace folder.

: The path of the folder the file is contained in, relative to the workspace folder. ${activeFolderLong} : The full path of the folder the file is contained in.

Output panel

Smart scrolling behavior in the Output panel is now more efficient. Scrolling is locked when you click anywhere in the Output panel and gets unlocked when you click in the last line.

Screencast Mode

There is a new Screencast Mode in VS Code, which highlights the cursor position and keystrokes. Screencast Mode (Developer: Toggle Screencast Mode) can be useful for demonstration purposes.

Editor

Smart Selections

We have worked on improving the implementation of Expand Selection and Shrink Selection from the Selections menu. We are in the process of adding an API so that language servers can specify selection steps based on their semantics knowledge. In addition, we have improved the default implementation as well.

Stay tuned, there is more to come as smart select is improved. Use the smart-select -label to see what we are working on.

References history

There is now a References: Show History command for the References view. It brings up Quick Pick with previous searches allowing speedy reruns of previous searches.

Reference CodeLens

When selecting a reference CodeLens, a peek editor opens. This can now be controlled with the references.preferredLocation setting. Its options are peek and view , the latter shows references in the new view.

Snippets descriptions

When authoring snippets with long descriptions, in the past you were forced to write a long single string. There was no support for using an array as you could for body . This has now changed and long descriptions can be written using string arrays.

{ "prefix" : "happy" , "body" : "#Happy Coding!" , "description" : [ "First Line" , "Second Line" , "Third Line" ] }

Removed legacy search mode

20 releases ago, we started using ripgrep for search in VS Code. Our old Node.js-based search implementation has still been available behind the setting search.useLegacySearch . But as Marie Kondo says, we must tidy up the things that no longer spark joy. If you have been using regex features like backreferences or lookahead, make sure to turn on the search.usePCRE2 setting.

Use simple text editor for editing settings as JSON

On a similar theme, now that we have had a settings UI for several releases, we are looking into simplifying the JSON settings editing experience. If you edit settings as JSON by opening a settings.json file, or clicking the {} button in the settings UI, or invoking the Open Settings (JSON) command, then you will get a simple JSON editor instead of the split JSON editor that we had previously. You can still see the listing of default settings with the Open Raw Default Settings command.

If you really miss the split JSON editor with the default settings on the left, you can restore it by enabling the workbench.settings.useSplitJSON setting. Note that you will always be able to edit settings as JSON if that's what you prefer.

Network proxy support for extensions

The setting Http: Proxy Support ( http.proxySupport ) now enables network proxy support for all extensions by default.

Languages

TypeScript 3.3

We now ship with TypeScript 3.3.1. This TypeScript update brings some important bug fixes and polish.

Removing the markdown.previewFrontMatter setting

The markdown.previewFrontMatter setting has been removed. The Markdown preview now always hides YAML frontmatter (this was the default setting for markdown.previewFrontMatter ).

Markdown extensions such as Markdown yaml Preamble and GitHub Markdown Preview render frontmatter as a table in the preview.

Semantic selection

Semantic selection is now available for HTML, CSS/LESS/SCSS, and JSON:

Integrated Terminal

Reflow support

The terminal will now wrap and unwrap lines when it is resized horizontally.

ConPTY support on Windows

Managing terminal processes via the Windows ConPTY API is now available as an opt-in option in the Windows Insiders fast ring (build number 18309+).

{ "terminal.integrated.windowsEnableConpty" : true }

This will use the ConPTY system provided by the Windows Console team as the backend for the terminal. Enabling this should fix many issues with the Windows terminal, particularly around color support, interactive applications, and shells that natively support VT sequences.

Here's a before and after of 256 ANSI color support in a WSL terminal:

On Linux and macOS, the terminal will now resolve links relative to the current working directory, not the initial directory of the terminal.

Find in terminal improvements

Find in the terminal now supports incremental "find-as-you-type" searching, as well as the ability to find multiple terms on a single line.

Improvements to commandsToSkipShell setting

Previously, the setting terminal.integrated.commandsToSkipShell was a list of all commands that would skip evaluation by the terminal and be handled instead by VS Code. This was awkward because you would need a list of 100+ commands in your settings file to change it. This is now changed to be a list of additions and deletions, so you only include the changes to the default list:

{ "terminal.integrated.commandsToSkipShell" : [ // Make ctrl+n open a new file when the terminal is focused "workbench.action.files.newUntitledFile" , // Send ctrl+e to the terminal "-workbench.action.quickOpen" ] }

New buffer implementation enabled

The TypedArray/ArrayBuffer-based terminal buffer introduced in v1.29 is now turned on and the old implementation has been removed. This should provide a good boost to throughput in the terminal as well as significantly reduce its memory footprint.

Debug and tasks

Custom command user input variables

The input variables introduced last milestone are a powerful mechanism to ask for user input in task or debug configurations. Initially, we made promptString and pickString input variables available.

In this milestone, we are introducing a new type of input variable command which runs an arbitrary command when an input variable is interpolated. Since commands can be contributed by extensions, it is now possible to extend user input variables by new implementations.

The following example shows how to use a user input variable of type command in a debug configuration that lets the user pick a test case from a list of all test cases found in a specific folder. It is assumed that some extension provides an extension.mochaSupport.testPicker command that locates all test cases in a configurable location and shows a picker UI to pick one of them.

{ "configurations" : [ { "type" : "node" , "request" : "launch" , "name" : "Launch Test" , "program" : "${workspaceFolder}/${input:pickTest}" } ], "inputs" : [ { "id" : "pickTest" , "type" : "command" , "command" : "extension.mochaSupport.testPicker" , "args" : { "testFolder" : "${workspaceFolder}/tests" } } ] }

Task output support split terminals

You can now configure tasks to show output in a split terminal panel instead of creating a new one. A task configuration can use the group attribute in the presentation section to define where the task's output should be shown.

If you run both of the two tasks below, they will show in a split terminal so you can see both of them at the same time:

{ "version" : "2.0.0" , "tasks" : [ { "label" : "Task One" , "type" : "shell" , "command" : "echo One && sleep 5000" , "problemMatcher" : [], "presentation" : { "group" : "groupA" } }, { "label" : "Task Two" , "type" : "shell" , "command" : "echo Two && sleep 5000" , "problemMatcher" : [], "presentation" : { "group" : "groupA" } } ] }

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.

Grid Layout for the Workbench

The workbench layout is being reworked to use the same grid layout used by the editors themselves. The work being done here will not only simplify the engineering work of maintaining the workbench layout in the long run, but also help us light up new experiences.

This milestone, we are shipping with one such experience to demonstrate something that can be achieved more easily with the new grid layout, toggling the editor area. With the experimental grid layout enabled ( "workbench.useExperimentalGridLayout": true ), there is a new command Toggle Editor Area, which hides the code editors. This allows you to create a VS Code terminal panel, which occupies the complete editor area as shown below:

If you open a file from the terminal using code file.txt , it will still pop open an editor just as you would expect. This feature is still a work in progress and there are known issues, but we encourage you to check it out and file issues. You can keep up-to-date with issues regarding this work with this query.

HTML and CSS custom data support

Since this feature is in preview, the settings, Contribution Points, and data formats are subject to change.

Today, front-end developers often code in a superset of HTML/CSS:

Web Components allow custom HTML elements such as <my-button type="alert"></my-button> .

. PostCSS allows custom CSS properties such as size and not-yet-standardized CSS features such as :any-link .

and not-yet-standardized CSS features such as . Various frameworks allow even greater flexibility in the source HTML/CSS.

In this iteration, we improved the HTML custom data support introduced in 1.30 and added CSS custom data support.

Use html.experimental.customData or css.experimental.customData to load custom data. ( html.experimental.custom.tags and html.experimental.custom.attributes are removed.)

or to load custom data. ( and are removed.) Alternatively, bundle the JSON into an extension with contributes.html.experimental.customData or contributes.css.experimental.customData .

or . Finally, if you are writing a Language Server that uses vscode-html-languageservice or vscode-css-languageservice, you can create the Language Service with custom data.

Custom data enhances VS Code's understanding of HTML/CSS. For example, with these HTML/CSS JSON contributions, VS Code could provide completion and hover for the custom HTML tag/attribute and CSS property/pseudoClass:

{ "version" : 1 , "tags" : [ { "name" : "my-button" , "description" : "My button" , "attributes" : [ { "name" : "type" , "description" : "My button type" , "values" : [{ "name" : "alert" }] } ] } ] }

{ "version" : 1 , "properties" : [ { "name" : "my-size" , "description" : "Compiles down to `width` and `height`. See details at https://github.com/postcss/postcss-size." } ], "pseudoClasses" : [ { "name" : ":my-link" , "description" : ":any-link pseudo class. See details at https://preset-env.cssdb.org/features#any-link-pseudo-class." } ] }

The above sample is available at octref/simple-customdata, while a more fully-featured sample is available at octref/svg-data.

These guides explain the data format and how to use them through settings and extension Contribution Points.

Guide for using HTML Custom Data

Guide for using CSS Custom Data

Extension authoring

Extensions change event

A new event extensions.onDidChange was added which fires when the extensions.all array changes. This can happen when extensions are installed, uninstalled, enabled, or disabled. See the No reload on extension install section.

/** * An event which fires when `extensions.all` changes. This can happen when extensions are * installed, uninstalled, enabled or disabled. */ export const onDidChange : Event < void >;

Note: Extension authors that introduce new contribution points should listen to this event and update the state of the workbench accordingly.

Open resources in a browser

We have observed that several extensions use node modules like opn or open to open a URL in a browser. Given the desire for this functionality, we have added a new API vscode.env.openExternal . It expects a URL and can be used to open website-links, mail-links, or application-url-handler. Also, file URLs are accepted to open them in their default app, like a PDF file.

// open default browser await vscode . env . openExternal ( vscode . Uri . parse ( 'https://github.com/microsoft/vscode/issues/66741' ) );

Note: Extension authors currently using the opn or open modules should switch to this new API.

Global storage path

An extension is now provided with a global storage path ExtensionContext.globalStoragePath that is pointing to a local directory with write/read access. This is a good option if you need to store large files that are accessible from all workspaces.

/** * An absolute file path in which the extension can store global state. * The directory might not exist on disk and creation is * up to the extension. However, the parent directory is guaranteed to be existent. * * Use [`globalState`](#_ExtensionContext.globalState) to store key value data. */ globalStoragePath : string ;

VS Code takes care of cleaning up this path when the extension is removed.

Note: Extension authors that currently use a custom file system location to store state across workspaces should switch to this new API.

CodeActionKind.intersects

The CodeActionKind.intersects method is useful to check if a CodeActionProvider should bother computing its Code Actions:

import * as vscode from 'vscode' ; export class OrganizeImportsProvider implements vscode . CodeActionProvider { public provideCodeActions ( document : vscode . TextDocument , range : vscode . Range , context : vscode . CodeActionContext , token : vscode . CancellationToken ): vscode . CodeAction [] { // Only return organize imports actions if they were explicitly requested // We can check this using `intersects`. if (! context . only || ! vscode . CodeActionKind . SourceOrganizeImports . intersects ( context . only )) { // Organize imports actions were not requested return []; } // Organize imports was requested ... } }

contributes.resourceLabelFormatters

Extensions can now contribute resource label formatters that specify how to display URIs everywhere in the workbench. For example, here's how an extension could contribute a formatter for URIs with scheme remotehub :

"contributes" : { "resourceLabelFormatters" : [ { "scheme" : "remotehub" , "formatting" : { "label" : "${path}" , "separator" : "/" , "workspaceSuffix" : "GitHub" } } ] }

This means that all URIs that have a scheme remotehub will get rendered by showing only the path segment of the URI and the separator will be / . Workspaces which have the remotehub URI, will have the GitHub suffix in their label.

Add arguments to keybindings

When defining a keybinding in package.json , you can now define arguments. Upon execution, those arguments are passed to the command.

In the sample below, it is: {foo: 1, bar: 2} .

"keybindings" : { "key" : "cmd+i" , "command" : "myCommand" , "args" : { "foo" : 1 , "bar" : 2 } }

Full control over createTerminal environment

The new setting TerminalOptions.strictEnv when set to true will not make any modifications to the terminal environment at all, instead it will be used exactly as passed in by the extension.

// This will create a terminal whose environment only contains the single value // FOO=BAR. const terminal = createTerminal ({ name: 'Test terminal' , env: { FOO: 'BAR' }, strictEnv: true });

The version of Electron that VS Code runs on has been updated which brings with it an update to Node.js from 8.9 to 10.2.0 . All extensions will now run on this newer version of Node.js. Take a look at Node v10.0.0 deprecations for a list of deprecations in Node.js 10.

We've updated our version of Octicons to 8.3.0 and now support the following icons:

$(arrow-both)

$(bold)

$(color-mode)

$(eye-closed)

$(fold-down)

$(fold-up)

$(grabber)

$(italic)

$(kebab-horizontal)

$(kebab-vertical)

$(note)

$(organization-filled)

$(person-filled)

$(project)

$(request-changes)

$(screen-full)

$(screen-normal)

$(smiley)

$(tasklist)

$(text-size)

$(unverified)

$(verified)

You can read our documentation to view a full list of the icons that we support. For a full detail list of changes, see the Octicon changelog.

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.

SignatureHelpContext.activeSignatureHelp

The proposed SignatureHelpContext.activeSignatureHelp field 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 before the signature help provider was retriggered.

Auto fix and CodeAction.isPreferred

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, often one of these Quick Fixes is the most reasonable fix for the problem. For example, fixing a spelling error is usually the more likely fix than generating new fields:

By using the proposed API, extensions can set isPreferred on a CodeAction to indicate that is the most reasonable fix for the underlying problem. 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, often the user just 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 proposed 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 autofix on save:

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

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

Debug Adapter Protocol

Proposed Debug Adapter Protocol for data breakpoints

As a follow-up step for the ongoing work on data breakpoints (AKA "watchpoints"), we made some progress on the design of the Debug Adapter Protocol for data breakpoints. The proposed DAP changes live on this branch and the corresponding TypeScript API can be found in the Data breakpoints proposal.

If you are interested in supporting data breakpoints in your debugger extension, please have a look at the proposal and provide feedback.

Live theme editing

When developing a color theme extension, you can see color changes applied live in the Extension Development Host window.

The same works for file icon themes.

Engineering

In this milestone, we finished the exploration of bundling Electron 3 into VS Code, making it the first time we ship this Electron version with stable. This is a major Electron release and comes with Chrome 66 and Node.js 10.x (a major leap forward compared to our current version that has Chrome 61 and Node.js 8.x).

At the same time, we started to explore updating to Electron 4, which we hope to push to Insiders soon.

Better performance information

With this release, the Developer: Startup Performance command output is presented in the editor and no longer in DevTools. That makes it easier to read and faster to get to. In addition, many issues with the information have been fixed.

WinJS.Promise removal ✅

When VS Code started, JavaScript wasn't what it is today. For instance, there were no native promises and so the team decided to use WinJS.Promise for asynchronous work. Today, the situation is different: native promises are real and WinJS.Promise is obsolete. Midway through last year, we started an effort to remove WinJS.Promise from the codebase, which we completed in December.

Strict null checking

We continued our work to strict null check the main VS Code codebase. Thanks to your help, this milestone we were able to enable strict null checking for a large number of test files, which eliminated a large number of errors.

We will be continuing the strict null check effort next milestone.

Contributions to Extensions

Our team maintains or contributes to a number of VS Code extensions. Most notably this month:

TSLint support

The new TSLint extension now supports auto fix on save using source.fixAll code actions.

"editor.codeActionsOnSave" : { "source.fixAll" : true }

We recommend that all users of the deprecated TSLint (eg2.tslint) extension migrate to the new TSLint extension.

Stylus language support

The Stylus language extension now uses the curated data from vscode-css-languageservice to offer up-to-date completions with status warnings and syntax documentation.

GitHub Pull Requests

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

Below are some of the new features:

GitHub Review support. You can now group comments into a review instead of just adding them individually.

The extension works seamlessly when you join a Live Share session when the workspace is a GitHub repository.

We introduced GraphQL gradually into the project so the description view now presents more detailed information of a pull request and the overall performance of the extension is improved.

You can now choose Create Merge Commit , Squash and Merge , or Rebase and Merge when merging a pull request.

, , or when merging a pull request. Performance improvements. We reduced both the API calls to GitHub and git operations when you browse pull requests, file changes, and checkout a pull request, which makes the extension respond faster, especially on Windows.

You can read the full release notes for the extension at vscode-pull-request-github releases.

New documentation

Python Jupyter Notebooks

A new Working with Jupyter Notebooks topic describes how to open, debug, and export Jupyter Notebooks from within VS Code.

Improved JavaScript and TypeScript documentation

We've refreshed our JavaScript and TypeScript articles to make sure they are up-to-date and provide more helpful information.

The JavaScript and TypeScript pages now provide an overview of the features that VS Code offers for these languages. More detailed explanations of these features and tutorials have been moved to new pages under Node.js / JavaScript and TypeScript respectively in the table of contents.

For extension authors, the VS Code API documentation was rewritten and moved to its own table of contents.

Here you'll find articles to:

Get you started with your first extension.

Learn about various extension capabilities.

Find extension guides and advanced topics.

Complete API references.

Notable fixes

7570: VS Code does not open offline

14372: Extensions: disablement state needs to be communicated across windows

34396: High CPU on single CPU VM

58167: Terminal and minimap restore textures are corrupted after resuming the OS

59794: Terminal screen reader support doesn't work when editor.accessibilitySupport is set to 'auto'

61649: Debug cannot read property 'onError' of undefined

63832: Unable to attach to lsp server when debugging extension

64948: GDB C/C++ debugger won't start, giving error

65697: Debug stopOnEntry with autoAttachChildProcesses is not honored on node cluster forked processes

66302: Ctrl + L should be bound to clear repl by default

66681: "Select for compare" and "Compare with selected" commands not shown for virtual documents

This release also include a security update for Microsoft Security Response Center CVE-2019-0728.

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-eslint :

Contributions to language-server-protocol :

Contributions to vscode-languageserver-node :

Contributions to debug-adapter-protocol :

Contributions to vscode-vsce :

Alexander (@usernamehw): Add colors to console messages PR #324

Contributions to vscode-json-languageservice :

@abc-55: Fixed a bug when comments are allowed but trailing commas aren't PR #35

Contributions to vscode-css-languageservice :

Contributions to vscode-html-languageservice :

Contributions to vscode-generator-code :

Contributions to vscode-recipes :

Contributions to localization :

There are over 600 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.