Nice feature!

I like it as well :) Thanks!

deprecated in favour of another extension or a setting. If a deprecated extension has this alternative extension or a setting the UI will guide users to migrate to the new extension or setting.

I can see how this flow works for full-on extension deprecation, but I do not have enough information to understand what the flow looks like for a deprecated setting. @isidorn Can you please provide an overview of what this flow would look like?

Suggestion for deprecation due to no longer being maintained:

tht13.gerrit-vscode
tht13/gerrit-vscode#14

As it's the first one that shows up in VS Code when searching for Gerrit, I suggest it to be marked as deprecated, especially because it no longer works.

Also, please deprecate my fork: felipecrs.vscode-gerrit

Although it works, I no longer maintain it.

It's not a direct replacement, nor was it arranged, but if you want to suggest a replacement, there you go:

SanderRonde.vscode--gerrit
https://github.com/SanderRonde/VSCode-Gerrit

@SanderRonder is doing a great job in this new one.

The extension heptio.jsonnet (repository) has been abandoned; there is a fork of it called Sebbia.jsonnetng (repository).

Please deprecate https://marketplace.visualstudio.com/items?itemName=freebroccolo.reasonml - it was so popular in it's day that it remains the top hit when searching for ocaml with 120,000 installs.

It hasn't been updated in 3 years, when the readme was updated to say it's unmaintained: https://github.com/reasonml-editor/vscode-reasonml/blob/master/README.md

The plugin the readme links to is also no longer maintained. I suggest https://marketplace.visualstudio.com/items?itemName=ocamllabs.ocaml-platform as the alternative extension to recommend instead.

1. In cases where the functionality was implemented directly to VS Code, it would be nice to acknowledge the effort of the extensions' authors since it's obvious those extensions were popular and useful enough that VS Code authors decided to implement them in VS Code directly.
2. Are the authors of the deprecated extensions notified in any way that their extensions are on the list of the deprecated extensions? Are the authors of the alternatives (when the extension is replaced by another one) notified that their extension is used as an alternative?

Hey!

My antfu.vue-i18n-ally and antfu.i18n-ally are depercated in favor of lokalise.i18n-ally

Thanks for rolling out this feature!

Please ensure to be open with the list of entries!

The list of deprecated extensions is maintained by the VS Code.

So... where it is actually maintained? Please post a link to a file.
I guess that would be in the marketplace team, or is it really vscode?

TSLint (deprecated) (eg2.tslint) should not recommend the ESLint extension instead. There is a substantial migration effort to move from TSLint to ESLint. We're working on it, but my team still has a number of old branches that we still need to maintain which use TSLint. The ESLint extension is not a replacement - it will not run TSLint rules.

I have tried migrating from eg2.tslint to ms-vscode.vscode-typescript-tslint-plugin in the past but was unsuccessful, probably because we use a workspace version of TypeScript and TSLint. (They're devDependencies in package.json.)

I'm aware that you want people to move to ESLint, and certainly not to start using TSLint at this point. However, I feel you should only deprecate an extension when the suggested replacement substantially replicates the functionality of the original without making changes to the user's wider environment.

Hi I am the maintainer of HaaLeo.vscode-stylint. It is a linter extension for the unmaintained linter stylint and therefore should be deprecated in favor for stylelint.vscode-stylelint. Thx :)

Hello, can you please remove the ms-vscode.vscode-embedded-tools extension please? I already unpublished it so I cannot link it. Please let me know if you need anything else.

I have already sent an email to vsmarketplace@microsoft.com and they asked me to post here. We don't have a direct replacement for this extension as there are specialized extensions depending on the user's embedded environment.

Hello, please deprecate the Ironman Software version of the PowerShell Universal extension. PowerShell Universal has been acquired by Devolutions and we will be publishing a new extension under that organization.

Extension to deprecate:

PowerShell Universal - Visual Studio Marketplace

Information about the acquisition:

PowerShell Universal Joins Devolutions

New extension:

We're sorry, the page you requested cannot be found.

Hi, can you please deprecate https://marketplace.visualstudio.com/items?itemName=Derpius.nanosworld

In favour of https://marketplace.visualstudio.com/items?itemName=go-horse-studios.nanos-world

cc: vsmarketplace@microsoft.com @satapathyj

Reaching out on that email now for auth

Thank you!

Hello,
we rebranded our tooling and would like to request several deprecations with new alternatives:

• SICK AppSpace SDK -> SICK App Designer
• SICK AppSpace Programmable Core -> SICK App Designer Core
• SICK AppSpace Lua Language Server -> SICK App Designer Lua Toolbox
• SICK AppSpace UI-Builder -> SICK App Designer UI-Builder
• SICK AppSpace Emulator -> SICK App Designer AppEngine Emulator

Thank you and kind regards
Dominik Breitling