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

[hallvictoria]

Hello, please deprecate vscode-azure-functions-remote-web-test. There is no replacement.

There's no repo linked, but I've been in contact with the [email protected] team to verify ownership.

[isidorn]

Done. Thank you!

[equinusocio]

Asking for deprecation of my extensions Equinusocio.vsc-material-theme and Equinusocio.vsc-material-theme-icons in lieu of "Vira Theme" (vira.vsc-vira-theme), all extensions are owned by me.

old: https://marketplace.visualstudio.com/items?itemName=Equinusocio.vsc-material-theme
new: https://marketplace.visualstudio.com/items?itemName=vira.vsc-vira-theme

old: https://marketplace.visualstudio.com/items?itemName=Equinusocio.vsc-material-theme-icons
new: https://marketplace.visualstudio.com/items?itemName=vira.vsc-vira-theme

I own all the extensions mentioned, and they have been merged into "Vira Theme":

CLICK TO EXPAND

---

If you know some extension which is deprecated you can also let us know and we will reach out to the respective extension author.

About this, there is also fredrikaverpil.vscode-material-theme which i don't own but is a deprecated fork of my extensions (to deprecate) that has been deprecated back in 2017 in favour of my extensions as mentioned in the readme.

Thank you a lot!

[Capel23]

thanks! very useful

[isidorn]

Done, thank you!

[equinusocio]

Thank you for your response. Could you please advise if there is a waiting period to allow the change to be propagated? I am still observing the extensions without the deprecation notice.

[isidorn]

Thank you. Yes there is a slight delay. Should be updated in a couple of hours.

[Tatsinnit]

Hiya @isidorn !! Thank you so much in advance!!

• Please deprecate the extension ⁠Bridge to Kubernetes

Gentle fyi to: @qpetraroia , @hsubramanianaks, @tejhan and @gambtho. ❤️ 🙏

[qpetraroia]

Thanks @isidorn, B2K is being retired on April 30th Azure/Bridge-To-Kubernetes#655. Can we make sure to do this on April 30th or later? Thanks!

[qpetraroia]

@isidorn can we deprecate the extension please? thank you!

[isidorn]

Done. Thank you.

[SeanCullen1]

Hi,
I have recently launched a new version of our Contrast Security ADO Pipeline plugin.

Can we please deprecate this old version https://marketplace.visualstudio.com/items?itemName=contrast-security.contrast-integration

This is the new version we would like customers to use going forward.
https://marketplace.visualstudio.com/items?itemName=contrast-security-ado.contrast-ado-pipeline-integration

Thank you,
Sean Cullen

[isidorn]

Done. Thank you

[SeanCullen1]

Hi @isidorn - what is the expected behaviour here if a plugin has been deprecated? should it redirect to the latest version?

[isidorn]

If the plugin is depreacted it will point to the replacement extension. Though this will only be rendered on the VS Code side. Not in the Marketplace yet.

[SeanCullen1]

perfect, how long does it take marketplace to update also? Thanks @isidorn

[isidorn]

Marketplace does not support deprecated extensions yet. I do not know when this feature will be exactly implemented.

[equinusocio]

Please deprecate Equinusocio.moxer-theme and Equinusocio.moxer-icons in lieu of "Vira Theme" (vira.vsc-vira-theme), all extensions are owned by me.

old: https://marketplace.visualstudio.com/items?itemName=Equinusocio.moxer-theme
new: https://marketplace.visualstudio.com/items?itemName=vira.vsc-vira-theme

old: https://marketplace.visualstudio.com/items?itemName=Equinusocio.moxer-icons
new: https://marketplace.visualstudio.com/items?itemName=vira.vsc-vira-theme

[isidorn]

Done. Thank you

[smocherla-brex]

Hi there,

Could you help deprecating SridharMocherla.bazel-kotlin-vscode-extension in favor of Brex.Bazel Kotlin which should be recommended. I'm the owner of the original extension and transferred the ownership.

Thanks,
Sridhar

[isidorn]

Done, thank you

[mechash]

Hello,

I'm Ashish Jaiswal - Tech Lead at Drona Aviation, I have a request to Deprecat our old extension Drona-Aviation.pluto-ide-beta in favour of drona-aviation.pluto-ide all the extension are developed and managed by me as the part of the Drona Aviation PVT. LTD.

old : https://marketplace.visualstudio.com/items?itemName=Drona-Aviation.pluto-ide-beta

new : https://marketplace.visualstudio.com/items?itemName=Drona-Aviation.pluto-ide

Thank you for the help here.

Best Regards,
Ashish Jaiswal (MechAsh)
Tech Lead
Drona Aviation PVT. LTD.

[isidorn]

Done, thank you

[DrMerfy]

Hello,

please deprecate https://marketplace.visualstudio.com/items?itemName=adammaras.overtype (it hasn't been developed since 2016, https://github.com/AdamMaras/vscode-overtype)
and its fork https://marketplace.visualstudio.com/items?itemName=DrMerfy.overtype
both are being replaced by the native overtype support (https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_96.md#overtype-mode)

Thanks in advance!

[isidorn]

Done, thank you

[jojohnso-msft]

Hello,

Please deprecate the old extension: https://marketplace.visualstudio.com/items?itemName=ms-ossdata.vscode-postgresql

Replace with the new extension: https://marketplace.visualstudio.com/items?itemName=ms-ossdata.vscode-pgsql

[isidorn]

Done, thank you

[luispDesktop]

Hi,

please deprecate https://marketplace.visualstudio.com/items?itemName=synopsys-codexm.coverity-codexm
replace with new extension https://marketplace.visualstudio.com/items?itemName=blackduck.blackduck-coverity-codexm

[isidorn]

Done, thank you

[McPatate]

Hi, we'd like to deprecate https://github.com/huggingface/llm-vscode in favor of, Copilot? 😄

(joke aside, no replacement!)

[isidorn]

Done. Thank you

[dentifrag]

Hello! We're looking to deprecate the Copilot Workspace extension between May 30th, 07:00 UTC and May 31st, 07:00 UTC, which is on the day in the continental US we are bringing down Copilot Workspace. Thank you! :)

[isidorn]

Is there some alternative extension we should point people to?

Also that timing will not happen since it is a weekend, and Friday I am out. We can probably deprecated start of next week.

[benjiegross]

We do not have an alternative extension to point people to since Copilot Workspace is going away. Would it be possible to get this deprecated today instead?

[isidorn]

Sure. Done. Should be live in an hour.

[DevJoaoLopes]

Hello, I would like to depreciate the following extension: bayon-component-generator in favor of Github Copilot 👍

Thank you!

[isidorn]

Done. Thanks