April 2022 (version 1.67)

Update 1.67.1: The update addresses this security issue.

Update 1.67.2: The update addresses these issues.

Downloads: Windows: x64 Arm64 | Mac: Universal Intel silicon | Linux: deb rpm tarball Arm snap

Welcome to the April 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:

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

Watch the release party: Listen in as the VS Code team discusses some of the new features. You can find the recording of the event on our YouTube channel.

Highlights short: If you just have 60 seconds, check out the April VS Code release highlights video to quickly see what's new.

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.


Explorer file nesting

The Explorer now supports nesting related files based on their names. There are several settings to control this behavior:

  • explorer.fileNesting.enabled - Controls whether file nesting is enabled at-large. It can be set either globally or for a specific workspace.
  • explorer.fileNesting.expand - Controls whether nested files are expanded by default.
  • explorer.fileNesting.patterns - Controls how files are nested. The default configuration provides nesting intelligence for TypeScript and JavaScript projects, but you're encouraged to modify this to fit your own project's structure. Some examples:

Default configuration:

.js and .min.js files nested under .ts file, tsconfig.test.json nested under tsconfig.json, package-lock.json nested under package.json

Nesting under index.ts when a file matches the directory's name ("index.ts": "${dirname}.ts"):

in directory named SomeFolder, SomeFolder.ts is nested under index.ts

Nesting files that have the same name as a different file but with an added segment ("*": "${basename}.*.${extname}"):

file1.test.myext is nested under file1.myext, file2.spec.other is nested under file2.other

Theme: GitHub Light High Contrast

File nesting has been available through an experimental setting for several iterations. The behavior now is mostly unchanged, except for file operations. The experimental setting explorer.experimental.fileNesting.operateAsGroup has been removed in favor of treating nests as a group when collapsed, but as single entities otherwise. This means that if you want to copy, cut, drag, or delete an entire nested stack of files, you can collapse the nest then operate on it as a single entity. When nested elements are expanded, selections will behave as normal.

Settings editor search filter button

The Settings editor search control now contains a funnel button on the right side. Clicking on the button shows a list of filters that you can apply to the search query in order to filter down the results.

Selecting the Settings editor filter button and then applying a language filter from the dropdown

Theme: Light Pink

Settings editor language filter indicator

Settings editor language filters now change the scope text to more clearly show which language is being acted on when a language filter is applied. The short video above shows the Markdown language filter (@lang:markdown) being applied to the filtered settings.

For reference, when a language filter is applied, modifying a setting's value will modify the value of that setting for that language only. Language-specific settings are scoped in settings.json by the language identifier:

  "[markdown]": {
      "editor.wordBasedSuggestions": "off"

Save files after refactoring

Refactorings, like Rename, often modify multiple files and leave them with unsaved changes (dirty). External development tools usually require these files to be saved. To make this workflow easier, there is a new setting files.refactoring.autoSave that defaults to true and controls if files that were part of a refactoring should be saved automatically.

Exclude dirty editors in editor limit

A new setting workbench.editor.limit.excludeDirty controls if the maximum number of opened editors should exclude dirty editors for counting towards the configured limit. The setting is disabled by default (false).

Bring back "Uncommitted Changes" to Timeline

When we introduced Local History feature last month, we removed the Uncommitted Changes entry from the Git timeline provider because it felt a bit redundant. However, some users see real value in this timeline entry and now you can bring it back by configuring the new git.timeline.showUncommitted setting accordingly.

New editor placeholder when opening fails

When an editor fails to open, VS Code no longer shows a notification and reveals the previous opened editor. Instead, there is a generic placeholder with the error message and, in some cases, actions to resolve the error.

Editor placeholder with the option to create a missing file

Language status improvements

The language status item now shows formatter conflicts - those happen when multiple formatters for a language are installed but none of them is configured as the default formatter. Also, the language status item is more prominent when containing severe status.

Animated language status with an error item for formatter conflicts

Additionally, the language status item will now show hints to switch languages when your document is suspected to be a different language than what is currently set. This applies only to untitled editors and notebook cells, and can be configured with the workbench.editor.languageDetectionHints setting. Below this is demonstrated in the Handy Dandy Notebook, which supports executing cells in various different languages.

demonstrating detecting various languages in a notebook

Theme: GitHub Light High Contrast

Show invalid or incompatible extensions

The Extensions view now shows invalid or incompatible extensions in the Installed extension list with error status. For example, if your VS Code version is 1.67.0-insider and you have installed an extension that requires VS Code version 1.68.0, then it will show up in the list with incompatible error status.

Incompatible extension details shown in the Extensions view item hover

Confirm before quit

A new setting window.confirmBeforeClose can be configured to show a confirmation dialog before quitting the application.

Confirmation dialog shown after using a keyboard shortcut to start closing VS Code

You can either chose keyboardOnly to bring up the confirmation dialog when a keybinding is used or always, even when using the mouse to quit.

Note: The setting is not entirely new and has been available in VS Code for Web for some time.

comments.openView default value

The old default value of comments.openView was file, which caused the Comments view to open every time a file with comments was opened. To make the Comments view less noisy, the new default is firstFile, which causes the Comments view to open only the first time a file with comments is opened during a session.

Multiline comments

Behind the scenes, VS Code has supported multiline comments since the comments UX was finalized, but multiline comments were never surfaced in the UI. You can now see and leave multiline comments.

Selecting multiple lines and leaving a comment

Handle URI in new window

Whenever a VS Code URI contains a query parameter windowId=_blank, VS Code will handle it in a new window. Example: vscode://vscode.git/clone?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode-vsce.git&windowId=_blank.


Bracket pair colorization enabled by default

Given the positive feedback of the new bracket pair colorization feature introduced in the 1.60 release, we enabled bracket pair colorization by default.

Side by side comparison with bracket pair colorization on and off

Bracket pair colorization can be disabled by setting "editor.bracketPairColorization.enabled" to false.

Bracket pair colorization can also be disabled just for specific languages:

"[typescript]": {
  "editor.bracketPairColorization.enabled": false,

TextMate grammars can mark tokens as unbalanced

Previously, TextMate grammars could not mark certain brackets as unbalanced, like the closing parenthesis in the case-statement of shell scripts:

Old behavior where unbalanced brackets not detected

To make bracket pair matching and colorization more robust, TextMate grammar contributions can now express that brackets in certain tokens should not be matched. In the contributes section of an extensions package.json, provided grammars can use the properties balancedBracketScopes (defaults to ["*"]) and unbalancedBracketScopes (defaults to []) to include or exclude scopes for bracket matching.

"grammars": [{
    "language": "shellscript",
    "scopeName": "source.shell",
    "path": "./syntaxes/shell-unix-bash.tmLanguage.json",
    "balancedBracketScopes": [ "*" ],
    "unbalancedBracketScopes": [ "meta.scope.case-pattern.shell" ]

With this feature, the grammar of the shell script can now indicate that ) in case-statements should not be matched:

New behavior correctly skipping a bracket that isn't matched

New bracket matching algorithm

Bracket matching now uses the same data structure as bracket colorization. This both increases accuracy and performance.

Old bracket matching behavior (notice that the colors and the highlight decoration do not match):

Old behavior with incorrect bracket matching

New bracket matching behavior:

New behavior with correct bracket matching

Bracket guide improvements

Horizontal bracket guides now properly support wrapped lines. Also, bracket pairs that only span a single line get their own horizontal bracket guide.

Horizontal bracket guides displayed for wrapped lines

Horizontal bracket guides are disabled by default and can be enabled with "editor.guides.bracketPairsHorizontal": true.

With this release, "editor.guides.highlightActiveIndentation" now accepts the value "always". If set to always, indentation guides are highlighted even if there is already an active bracket pair.

Toggle inlay hints

Inlay hints are a great way to show additional information right within your source code. However, sometimes you just want to see the actual source code. To support quickly hiding inlay hints, the editor.inlayHints.enabled setting has been changed: in addition to on and off, there are also values onUnlessPressed and offUnlessPressed. The on/offUnlessPressed values hide or show inlay hints while Ctrl+Alt is being pressed and held.

Editor › Inlay Hints: Enabled value:

  • on - Inlay hints are enabled.
  • off - Inlay hints are disabled.
  • onUnlessPressed - Inlay hints shown and hidden with Ctrl+Alt.
  • offUnlessPressed - Inlay hints hidden and shown with Ctrl+Alt.

Improved inline suggestions

Last month we added the ability to use 👻 ghost text (faint coloring) for quick suggestions. Reminder: you need to use inline for the editor.quickSuggestions setting. We have done some polish work in this area, notably trigger characters and TypeScript "complete functions with arguments" are now supported.

Trigger characters and ghost text

To disable IntelliSense when typing trigger characters, like ., set "editor.suggestOnTriggerCharacters": false. To enable TypeScript function call completions, use "typescript.suggest.completeFunctionCalls": true.

Drag and drop text into editor

You can now drag and drop text from other applications into a text editor. On macOS for example, this lets you drop an emoji from the emoji panel into a text editor:

Dragging and dropping an emoji into VS Code

While dragging, a dotted cursor shows you where the text will be inserted.


Find result count

When searching in the terminal, the result count and currently selected match index are now displayed in the Find control.

Text is searched for in the terminal and the Find control is labeled match 12 of 14 to indicate that match 12 is currently selected

Source Control

Source Control Repositories view

This milestone we have introduced a new setting, scm.repositories.sortOrder, to control the default sort order of the repositories displayed in the Source Control Repositories view. Repositories can be sorted by the order in which they are discovered, by name, and by full path. Changing the sort order can be done using the ... Views and More Actions menu of the Source Control Repositories view and the ... > View & Sort > Repositories menu of the Source Control view.

The short video below shows that the SCM > Repositories: Sort Order setting is by default discovery time, the time when the repositories were selected, and that you can also change the sort order in the Source Control views.

Sort repositories in the Source Control Repositories view

Editor decoration improvements

Last milestone we improved the accessibility of the editor decorators for added/modified lines by adopting a pattern for the modified line decorators. This milestone, we added a new setting, scm.diffDecorationsGutterPattern, that lets users toggle the pattern for the editor decorators.

Toggle editor decorator settings for added/modified lines

The setting defaults to using the pattern for the modified line decoration but not for added:

"scm.diffDecorationsGutterPattern": {
    "added": false,
    "modified": true

Performance improvements

Users that have the git.untrackedChanges setting set to hidden will experience better performance when working with large repositories. This is achieved by passing the -uno parameter when calling git status.

Expanded remote source providers API

The Git extension API now allows extensions that register or display remote source providers to provide richer information about remote sources.

Remote source providers can now set the description and icon for individual remote sources. Additionally, providers can optionally specify recent remote sources. These are displayed at the top level in the picker for easy access and sorted by timestamp if one is provided.

The expanded API has been adopted by the built-in GitHub extension, as well as the GitHub Repositories and Azure Repos extensions in github.dev and vscode.dev.

Clone from GitHub using SSH

A new setting github.gitProtocol lets you change the default protocol when cloning a repository from GitHub. The value is https by default but can be changed to ssh.


Auto-expand lazy variables

A couple months ago, we added support for clicking a button to expand "lazy" variables in the debugger Variables view. There is a new setting, debug.autoExpandLazyVariables, to automatically expand lazy variables without a click.

New button for lazy variables

We've updated the text link button to a real button with the "eye" codicon. The "eye" codicon was also updated to look more eye-like.

A button to expand a lazy variable

Shift-click to disable breakpoints

You can now Shift+Click on a breakpoint (or conditional breakpoint, or logpoint) to disable it, and to re-enable it.

Shift clicking on breakpoints to disable and re-enable them


You can now quickly create Markdown links by dragging and dropping files from VS Code's Explorer into a Markdown editor. Hold Shift while dragging the file over a Markdown editor to drop it into the editor and create a link to it:

Inserting links into Markdown by dragging and dropping from the Explorer

If the file looks like an image, VS Code will automatically insert a Markdown image. Otherwise a normal Markdown link is added.

This also works when dragging some types of files from other applications, such as dragging and dropping images from a web browser:

Dropping a image from a web browser into VS Code to add a Markdown image

You can disable this drop behavior by setting "markdown.editor.drop.enabled": false.

Markdown: Find All References to headers

VS Code now supports running Find All References in Markdown files for headers. This lets you see all the places where a given header is used within the current workspace, including links to it from other Markdown files.

To get started, place your cursor either on the header itself or on the fragment part of a link to the header (for example, #some-header in [link text](#_some-header) or [link text](/path/to/file#some-header)) and run Find All References.

Finding all references to a Markdown header

This will show all references in the References view. If you prefer a different view, you can also use the Peek References or Go to References commands.

VS Code also supports finding all references to reference links within the current file. This is supported for:

  • On ref in [some text][ref].
  • On ref in the shorthand link [ref].
  • On ref in the link definition [ref]: http://example.com.

Finding all places a Markdown link reference is used

Markdown: Find all references to files

You can also now find all the references to a given Markdown file in the current workspace. Again this includes links across files.

This can be triggered in a few ways:

  • To find references to the current Markdown file, use the Markdown: Find File References command.
  • To find references to a Markdown file in the Explorer, right-click on it and run Find File References command.
  • Run Find All References on the file part of a link to a Markdown file, such as [text](/link/to/file.md).

Finding all references to a Markdown file

This will list all places where a given file is referenced, including references to headers within that file.

Markdown: Find all references to URLs

Finally, we also support finding all places where a given URL is used in the current workspace.

Finding all places where a URL is used in Markdown files

Markdown: Rename headers

Ever change a header in a Markdown file only to realize that you also accidentally broke all links to it? That's where our new rename support for Markdown can help.

To get started, place your cursor on a header and then press F2 to start a rename. Enter the new text for the header and then press Enter to accept. This will both update the current header as well as updating all known links to it in the current workspace.

Renaming a Markdown header using F2

You can trigger renames on the header itself or on the header component of a link to the header. For example, some-header in [link text](#_some-header) or [link text](/path/to/file#some-header).

You can also rename reference links in Markdown. This will update all the reference links in the current Markdown file:

Renaming a Markdown link reference using F2

Markdown: Rename files

Rounding out our new Markdown rename support, you can now use F2 on file paths in Markdown links to both rename the file on disk as well as updating all Markdown references to it:

Renaming a file by pressing F2 on the file path in a link

Currently renaming files is only supported using F2 on a link to the file in the text editor. In upcoming iterations, we also plan to support update links when a rename is triggered in the Explorer.


The new setting json.validate.enable lets you turn off the JSON validation.

VS Code for the Web

Open Remote Repository picker

VS Code for the Web now respects the window.openFoldersInNewWindow setting when you use the Open Remote Repository picker. This aligns the picker behavior with the other versions of VS Code and replaces the Open in New Window Quick Pick item button.

Contributions to extensions


Inlay hints

The Java language service included in the Extension Pack for Java now supports inlay hints to show parameter names for method signatures.

Java file with parameter name inlay hints displayed for literal arguments, displayed for all arguments, and disabled

There are three modes for Java parameter name inlay hints:

  • literals - Enable parameter name hints only for literal arguments (default).
  • all - Enable parameter name hints for literal and non-literal arguments.
  • none - Disable parameter name hints.

Lazy variable resolution

The Debugger for Java extension now supports 'lazy' variables. This feature lets you defer the operations for an expensive variable until you explicitly expand the debugger UI to see it's value.

Debugger for Java supporting lazy variable resolution during a debugging session


Jupyter PowerToys extension

We are excited to announce the Jupyter PowerToys extension that provides experimental functionality for working with Jupyter notebooks. In its first release, we have prototyped the following features:

  • Kernel management panel
  • Contextual help
  • Execution grouping

We'd love for you to take these for a spin and let us know what you think so that we can hone them into a supported feature someday!

For more information, refer to the README in the vscode-jupyter-powertoys repository.

Web extension

The Jupyter extension can now be installed as a web extension for use with vscode.dev. Functionality is currently limited with support only for notebooks (.ipynb files) being run on Jupyter servers that do not require https.

If you'd like to experiment with the functionality, launch Jupyter from your local machine with:

jupyter --no-browser --NotebookApp.allow_origin_pat=https://.*\.vscode-cdn\.net

And connect to it using the command Jupyter: Specify Jupyter server for connections.

In upcoming releases, we will be enabling more features when running in a browser, including:

  • 'https' based servers
  • IntelliSense
  • Data viewing
  • Variable viewing
  • Interactive window
  • IPyWidgets
  • Plot viewing
  • Exporting

Jupyter kernel handling

A number of updates were made to Jupyter kernel handling:

  • To make it more obvious when a kernel has crashed, the extension now displays this information in cell output.
  • There is now troubleshooting guidance in cell output when certain known errors are detected during execution.
  • Solving kernel execution problems can be a tricky and time consuming process. We've put together a troubleshooting section on our wiki that we hope can help guide you to a solution quicker. Our GitHub Discussions forum can be a great resource for obtaining help as well.


No reload when changing language servers

The Python extension now supports updating the value of the python.languageServer setting and automatically restarting the language server without needing to reload VS Code.

Black formatter extension

There is now a Black Formatter extension that provides formatting support for Python using the black formatter. A pre-release version of the extension is available to install.

Import organization with isort

New isort extension, which provides import organization using the isort library. A pre-release version of the extension is available.

Remote Development

Work continues on the Remote Development extensions, which allow you to use a container, remote machine, or the Windows Subsystem for Linux (WSL) as a full-featured development environment.

You can learn about new extension features and bug fixes in the Remote Development release notes.

GitHub Pull Requests and Issues

Work continues on the GitHub Pull Requests and Issues extension, which allows you to work on, create, and manage pull requests and issues. Highlights of this release include:

  • Multiline comments
  • Showing commit changes in a tree

Check out the changelog for the 0.42.0 release of the extension to see the other highlights.

Preview Features

Settings Profile

In this milestone, we introduced Settings Profile that is a collection of your settings, extensions, and UI customizations. If you customized VS Code, you can now export your customizations to a Settings Profile file (mysetup.code-profile) and save it to your computer and share it with others.

The following short video shows exporting a Settings Profile from VS Code:

Export Settings Profile

You can also import a Settings Profile file to restore your customizations.

Below shows importing a Settings Profile into VS Code:

Import Settings Profile

You can host your Settings Profile file in the cloud, for example save it as a public GitHub gist, and share the URL with others. One can import the Settings Profile file by providing the URL.

Note: At present, only the following UI customizations are included in the Settings Profile. More will be added in the future.

  • Status bar items visibility
  • Activity Bar, Bottom Panel & Side Panel items visibility and order
  • Views visibility, location and order

TypeScript 4.7 Support

This update includes support for the upcoming TypeScript 4.7 release. See the TypeScript 4.7 iteration plan for more details on what the TypeScript team is currently working on. Some highlights:

  • Jump directly to a JavaScript implementation of a library function using the new Go to Source Definition command. You can learn more about this feature and share feedback in TypeScript issue #49003.
  • Snippets for completing methods as object members.
  • Group-aware Organize Imports.

To start using the TypeScript 4.7 nightly builds, install the TypeScript Nightly extension.

Extension authoring


We have finalized the read-only side of the tabs API (closing a tab is also supported) marking the completion of one of our most upvoted issues microsoft/vscode#15178. This exposes information such as how many groups there are, what tabs are open, what tabs are active, what type of editors a tab represents, and more! More information can be found in the vscode.d.ts file with the entrypoint into the API being window.tabGroups.

Notebook change and save events

We have finalized two notebook-related events:

  • vscode.workspace.onDidSaveNotebookDocument - An event that fires whenever a notebook has been saved.
  • vscode.workspace.onDidChangeNotebookDocument - An event that fires whenever a notebook has been changed. That includes structural changes, like adding or remove cells, as well as cell changes, like changing output or metadata.

Support for non-recursive workspace file watchers

In previous milestones, we announced that the createFileSystemWatcher API can be used to watch any folder on disk as long as the folder is not inside the opened workspace. We have now relaxed this restriction and allow non-recursive file watchers anywhere, even inside the opened workspace. Non-recursive watchers have the advantage that configured settings for excludes (files.watcherExclude) do not apply so you can be sure that the file watcher will only emit for the paths you subscribe to.

We are working on full support for recursive watchers with custom exclude rules for extensions, so stay tuned for more!

UX Guidelines

The UX Guidelines for extension authors has been redone to have its own table of contents, where you can find best practices for using the various VS Code user interface elements. Specific topics discuss the recommended Do's and Don't's when creating UI for your extensions so that they seamlessly integrate within VS Code.

Command Palette UX Guidelines on code.visualstudio.com

Running extension tests

Before, VS Code would exit the extension host process as soon as test running was finished. Now, when running extension tests, VS Code will first go through the regular deactivate flow and only afterwards exit. This allows extensions that spawn processes to better clean up after themselves.

Dropping files into custom trees

Building on the recently finalized tree drag and drop API, we now have basic support for dropping files from the OS into extension tree views using the text/uri-list MIME type.

Debugger extension authoring

UI for supportSuspendDebuggee and supportTerminateDebuggee

The disconnect request has two extra options that enable a client to control what happens to a debuggee when disconnecting:

  • suspendDebuggee indicates whether the debuggee should stay suspended after disconnection.
  • terminateDebuggee indicates whether the debuggee should be terminated when the debugger is disconnected.

A debug adapter can use the capabilities supportSuspendDebuggee and supportTerminateDebuggee to signal that it supports these options. When supported, a dropdown will appear next to the stop button in the debug toolbar with extra disconnect commands.

For example, in a "launch"-type debug session, for a debug adapter that supports both capabilities, the default toolbar button will be the normal Stop button, but the dropdown will include Disconnect (terminateDebuggee: false) and Disconnect and Suspend (terminateDebuggee: false, suspendDebuggee: true).

A dropdown with extra disconnection commands

Language Server Protocol

Support for notebooks and pull diagnostics has been moved out of the proposed state to be ready to ship the 3.17 release. New versions of the corresponding client and server libraries have been published to npm.

Proposed APIs

Every milestone comes with new proposed APIs and extension authors can try them out. As always, we want your feedback. Here are the steps to try out a proposed API:

  1. Find a proposal that you want to try and add its name to package.json#enabledApiProposals.
  2. Use the latest vscode-dts and run vscode-dts dev. It will download the corresponding d.ts files into your workspace.
  3. You can now program against the proposal.

You cannot publish an extension that uses a proposed API. There may be breaking changes in the next release and we never want to break existing extensions.

Drop into editor

The proposed text editor drop API lets extensions handle drops into text editors. These drop events can come from within VS Code—such as dragging a file from VS Code's Explorer into a text editor—or can be generated by dropping a file from your operating system into VS Code.

Using the drop extension sample to create a list of dropped files names

This iteration we've switched this API to a provider based model. We've also created a new extension sample that demonstrates how to use this api.

Badges on views

The new proposal for adding badges to views is available to try out. Similar to how badges work on views provided by VS Code core, extensions can use this API proposal to add number badges to views.


Playwright for Electron smoke tests

We have been using Playwright for our web-based smoke tests for a long time. However, our Electron-based smoke tests were still relying on our own custom solution. With the Electron support in Playwright, we were able to reuse most of our web-based smoke test code and use it for our Electron smoke tests too. We are excited to now use the Trace Viewer to diagnose failing smoke tests post-mortem.

New localization pipeline for extensions

VS Code supports a number of display languages that you can enable by installing a language pack. These are great for localizing VS Code itself and built-in extensions to VS Code. This iteration, we have started the standardization effort for localizing extensions that aren't built-in that the team owns. You'll see the results of this effort in the GitHub Repositories and Azure Repos extensions as their common dependency extension, Remote Repositories, is the first extension to onboard to this.

Next iteration, we will continue this standardization effort and onboard more extensions. The Python extension is currently in progress and GitHub Repositories and Azure Repos will be quick to follow. We want to get to a point where every extension owned by the team is localized and any new extension created in the future will be able to onboard with ease so that users who aren't native English speakers can have a great experience in VS Code.


Rust in VS Code

There is a new Rust in Visual Studio Code topic describing Rust programming language support in VS Code with the rust-analyzer extension. The rust-analyzer extension includes rich language features such as code completions, linting, refactorings, debugging, and more.

rust-analyzer extension for Visual Studio Code details pane

Notable fixes

  • 114844 Allow to skip restore editors from previous session from crash dialog
  • 127936 Allow to set files.encoding as language specific setting for files on startup
  • 138461 Emmet autocomplete inside a pair of [ ] in a React file is wrong
  • 139392 Confirmation of Clear Recent projects
  • 139950 When a breakpoint is hit, the caret (cursor) should move to that line
  • 145265 Terminal on Windows uses cmd /C, this corrupts passed arguments
  • 146406 Powerline symbols in the terminal get wrong colors
  • 146977 Declare folder support in Info.plist on macOS
  • 147104 Unable to finish logging in to GitHub

Thank you

Last but certainly not least, a big Thank You to the contributors of VS Code.

Web extensions

Extension authors for enabling extensions that run code as web extensions (the list below is between March 28 2022 and May 1 2022):

Issue tracking

Contributions to our issue tracking:

Pull requests

Contributions to vscode:

Contributions to vscode-css-languageservice:

Contributions to vscode-generator-code:

Contributions to vscode-js-debug:

Contributions to vscode-pull-request-github:

Contributions to debug-adapter-protocol:

Contributions to language-server-protocol:

Contributions to monaco-editor: