Deprecated extensions

[isidorn]

We now support deprecating extensions.

An extension can be just deprecated or 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.

For now the extension will not be rendered as deprecated in the Marketplace. Support for this will come later.

In order to mark your extension as deprecated please reach out to us. You can also comment in this discussion.
If you know some extension which is deprecated you can also let us know and we will reach out to the respective extension author.

VS Code will not automatically migrate or uninstall deprecated extensions. Instead it will provide the following UI.

[v1ctorio]

Nice feature!

[isidorn]

I like it as well :) Thanks!

[ericdrobinson]

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?

[isidorn]

@ericdrobinson good question. If an extension is deprecated in favour of a setting it would look like this
You can try it out by trying to install "Bracket Pair Coloriser" extension

[ericdrobinson]

Ahh, that is very helpful! Thanks very much!

[0num4]

This feature is no longer available, how can I use the old extension?
I want to use vscode-github
instead of "GitHub Pull Requests and Issues" extension due to "open in github" feature.

how can I use the old extension?

finally, I installed by use vsix.
but, really necessary feature was in https://marketplace.visualstudio.com/items?itemName=ziyasal.vscode-open-in-github

[yennhi2906]

@ericdrobinsoncâu hỏi hay. Nếu một tiện ích mở rộng bị loại bỏ để ủng hộ một cài đặt thì nó sẽ trông như thế này Bạn có thể thử bằng cách thử cài đặt tiện ích mở rộng "Bracket Pair Coloriser"

[felipecrs]

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.

[scentoni]

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

[TheSpyder]

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.

[KnisterPeter]

Hi,

I'm the maintainer of vscode-github which is deprecated and should be replaced by GitHub Pull Requests and Issues.

[cclauss]

How do we uninstall the deprecated extension?

[zcernigoj]

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?

[antfu]

Hey!

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

Thanks for rolling out this feature!

[GitMensch]

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?

[MikeDimmickMnetics]

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.

[HaaLeo]

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

[isidorn]

I have verified all the extensions that @felipecrs @scentoni @TheSpyder @KnisterPeter @antfu @HaaLeo are indeed deprecated and have marked them as such.
@MikeDimmickMnetics you are right. I have updated tslint to just be deprecated, not deprecated in favour of eslint

@GitMensch this is maintained on an internal CDN by the VS Code team as a short term solution. Soon the Marketplace will support this and then any extension author will be able to mark their extension as deprecated using the Marketplace UI.

@zcernigoj

1. We have already acknowledged the efforts of the extension authors before implementing it in VS Code. Before we do any of these features in VS Code we always first reach out to the extension author and only then proceed. Please check out our older release notes or discussions in respective GH repositories.
2. Yes, deprecated extensions get notified. The alternatives do not get notified.

Thank you very much ❤️

[GitMensch]

Thank you for clearing this up a bit.
Can you please mirror the list from your internal CDN somewhere?

[Snooz82]

Hi,
i am the maintainer of Snooz82.rf-intellisense
Please deprecate it and in favor of d-biehl.robotcode

I would actually also consider the following Robot Framework Extensions as being deprecated:
And those feature sets are typically Syntax Highlighting, Code Completion, GoTo and formatting features, which all implemented in
d-biehl.robotcode
So if the original maintainers are fine with naming RobotCode as a successor, i think that would suite the most users of these old plugins.

• TomiTurtiainen.rf-intellisense
  This is the one that i originally forked, because it was no longer maintained. The former maintainer also agree that it is not maintained anymore.
• keith.robotframework
  This is not compatible to current Robot Framework anymore.
• vivainio.robotframework
  Really old stuff
• JacobPhilip.danfoss-robotframework-debug
• kmk-labs.robotf-extension
  Super nice extention back in 2017. Not maintained and not really compatible to newer language features of the last years.
• yokey.robotf-souche-extension
  Fork of the former one, but not really better maintained.

Other deprecated Tools for Robot Framework:

• allyusd.robot-framework-helper
• robotframeworkbambouna.vscode-rf-bam-formatter
  This formats the code without compatibility to new language features of the last two year releases and does not follow languages best practices.

Thanks!

[sainiashu]

Hi @isidorn

Could you please move this extension "TomiTurtiainen.rf-IntelliSense" to the available installation list? As we are using it religiously in our development code.
Recently we saw that the extension was deprecated when we tried to install one of my colleague's systems. Also, we installed the Robot Code. However; it had some issues.

Please make it available for the installation ASAP.

Thanks

[sainiashu]

Hi @isidorn

Any update about my query? Our organization uses this extension "TomiTurtiainen.rf-IntelliSense" frequently and it affects our development work.

[isidorn]

We will change to mark it as deprecated but still allow install.

[fabioz]

@isidorn I I just saw that things such as Robot Framework Intellisense are deprecated in favor of Robot Code.

I think this is misleading.

The most used and active extension for Robot Framework right now is Robot Framework Language Server (I'm the current author for it), so, either those extensions should just be marked as deprecated without a favorite or they should be marked as deprecated in favor of Robot Framework Language Server...

[isidorn]

That's a fair point. We will just mark them as deprecated without a favourite. Thank you

[connorshea]

I would like to request the deprecation of https://marketplace.visualstudio.com/items?itemName=connorshea.vscode-ruby-test-adapter in favor of the Ruby LSP extension from Shopify, which includes similar test functionality for Ruby projects: https://marketplace.visualstudio.com/items?itemName=Shopify.ruby-lsp

You can see the deprecation notice in the repo for my extension here: https://github.com/connorshea/vscode-ruby-test-adapter

[v-sulagnapal]

Thanks for reaching out. Can you reach out to [email protected] to verify ownership using an alternate method and then we will complete the deprecation.

[andysterland]

I would like to deprecate the following extensions superseding them all with github.copilot-chat

• VisualStudioExptTeam.vscodeintellicode - IntelliCode
• VisualStudioExptTeam.vscodeintellicode-completions - IntelliCode Completions
• ms-dotnettools.vscodeintellicode-csharp - IntelliCode for C# Dev Kit
• VisualStudioExptTeam.intellicode-api-usage-examples - IntelliCode API Usage Examples

Fyi @isidorn @noellelc

[v-sulagnapal]

Done, Thank you!

[gesslar]

gesslar.vscode-gludoc requires removal, please. I have already unpublished it from the marketplace. repo is also deleted.

[sebastianrath]

Hey there, I’m the maintainer of Actionforge. The VS Code extension is currently unmaintained.

I’ve just added the deprecation flag here: https://github.com/actionforge/vscode-ext/blob/76d95708c144afcbb78b47304c4c5c7b597c976b/package.json#L13

Thanks!

[v-sulagnapal]

Done, Thank you!

[Barbapapazes]

Hello,

I'm the creator of Utils AI and I would like to deprecate it.

Extension: https://marketplace.visualstudio.com/items?itemName=barbapapazes.utils-ai-vscode
GitHub: https://github.com/Barbapapazes/utils-ai

This extension is deprecated and will no longer be maintained. Please consider using build-in prompts features of your editor instead.

Thank you!

[v-sulagnapal]

Done, Thank you!

[ai-defenter]

Hello,

We would like to deprecate https://marketplace.visualstudio.com/items?itemName=mcpower.mcpower 🙏
It is now replaced by https://marketplace.visualstudio.com/items?itemName=defenter.defenter-vsc

You can see the rename commit (from MCPower to Defenter) here.
Also, if you will go to the previous org and repo name (https://github.com/MCPower-Security/mcpower-proxy) you will be redirected to the new org and repo name (https://github.com/Defenter-AI/defenter-proxy)

[v-sulagnapal]

Thanks for reaching out. Can you reach out to [email protected] to verify ownership using an alternate method and then we will complete the deprecation.

[berikiushi]

Hello,

I would like to deprecate the extension due to loss of access to publisher account: https://marketplace.visualstudio.com/items?itemName=berikiushi0213.bronokai-theme

It is now replaced by: https://marketplace.visualstudio.com/items?itemName=berikiushi.bronokai-dark-theme

The repository is still the same: https://github.com/berikiushi/vscode-bronokai-theme

Thank you!

[v-sulagnapal]

Thanks for reaching out. Can you reach out to [email protected] to verify ownership using an alternate method and then we will complete the deprecation.

[Kiraalla]

I am the maintainer of '自由の助手'https://marketplace.visualstudio.com/items?itemName=kira0522.freedom-aide
Please deprecate it
I will publish a new one with the same name later

[v-sulagnapal]

Thanks for reaching out. Can you reach out to [email protected] to verify ownership using an alternate method and then we will complete the deprecation.

[mg0x7BE]

[v-sulagnapal]

Thanks for reaching out. Can you reach out to [email protected] to verify ownership using an alternate method and then we will complete the deprecation.

[v-sulagnapal]

Done, Thank you!

[nfode]

Hello,

I am the maintainer of https://marketplace.visualstudio.com/items?itemName=nickfode.latex-formatter. Here is the archived GitHub Repo: https://github.com/nfode/latex-formatter.

Please deprecate the exertion.

Thank you!

[v-sulagnapal]

Done, Thank you!

[robole]

Please deprecate the following extensions without replacements:

• robole.javascript-snippets
• robole.markdown-shortcuts
• robole.marky-markdown
• robole.marky-dynamic

I already made this request for each extension by email to [email protected].

The reply stated:

Hi ,
Thank you for contacting the Visual Studio Marketplace Support Team. We suggest adding the ask to VS Code [Deprecated extensions]](Deprecated extensions · microsoft/vscode-discussions · Discussion #1 ) and we will be happy to take care of the change. There you can also recommend an alternative extension to download in lieu of this one.
Regards,
VS Marketplace Support Team.
(representative:655cd9f9 )

[Qualyyy]

Hello,
I would like to deprecate this extension in favor of the new one
Thank you!

[v-sulagnapal]

Done, Thank you!

[alvaroyurrita]

Hello,
I am wondering if it is possible to deprecate these extensions

• Crestron S+: The new one below is a fork of this one. I contacted the owner and he agreed to the deprecation in favor of the one below since he is no longer maintaining it.
• Crestron Simpl+: It was last updated on 2018 and the owner cannot be reached. The one suggested has all the functionality of this extension.
• Crestron Simpl+ Code Snippets): It was last updated on 2018 and the owner cannot be reached. The one suggested has all the functionality of this extension.
• Simpl+ Formatter: It was last updated on 2022 and the owner cannot be reached. The one suggested has all the functionality of this extension.

All of the above should be deprecated in favor of this new one that is actively maintained by me.

[v-sulagnapal]

Thanks for reaching out. Can you reach out to [email protected] to verify ownership and confirmation from owners of each mentioned extension, then we will complete the deprecation.

[ptimoney]

Can you deprecate this extension:
https://marketplace.visualstudio.com/items?itemName=patrickt.hledger-tools

in favor of its replacement:
https://marketplace.visualstudio.com/items?itemName=patrickt.hledger-lsp-vscode

Both maintained by me

[v-sulagnapal]

Done, Thank you!

[DrBlury]

Can we deprecate this extension for now?
vscode-proto3
In favor of protobuf-vsc
The owner of said extension has not been maintaining the extension for a long time and I created a new one with its features and more. I just became a maintainer of the old one to help users that are still using this extension have something a little more stable. But I can not release a new version. Deprecation would be a good option I think.

[DrBlury]

The owner of said extension agreed to archive the extension. No further updates will be published and it should be marked as deprecated.
zxh0/vscode-proto3#184

[v-sulagnapal]

Done, Thank you!

[DrBlury]

@v-sulagnapal a lot of people are giving 1/5 star reviews because of the recommendation process and they fear a supply chain attack. These do not review the extension in itself, can something be done about that? :/

[cjc7373]

People have raised many concerns about the new extension. zxh0/vscode-proto3#184 now has at least 10 different people question the code quality of the new extesnion. But @DrBlury declined to respond to community's request, which is to remove the deprecation status of the original extension.

[DrBlury]

@cjc7373 I have responded to every review and asked for constructive criticism in the form of bug reports or feature requests. All raised issues were addressed within 24 hours of their initial posting. The reviewers sadly did not open any issues on Github, nor did they communicate their issues with the new extension in any other way. The deprecation of the old extension is the right step as it has not been maintained for the last 4 years and there are features that this extension is missing. Since protobuf evolved with protobuf editions and autocomplete for these... This makes the new extension a good replacement, as these are properly addressed and we already achieved feature parity before the deprecation was requested. The owner of said extension also confirmed that there will be no future release. If you find issues that disrupt your workflow, you are free to either install the deprecated extension again, open an Issue for the new... Or choose another extension that may suit your needs better. Reviewing bombing the extension negatively just to get your point across and not following up on the responses you get is not the proper way to handle this.

We want to have an extension that is truly a superior replacement to the old extension, which is why we need feedback from the community. If there are things that I missed or bugs that I oversee, please report them.
Thanks for reading. This is off-topic btw.