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

[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

[vaisriva]

Please deprecate,

Ciena: Blue Planet
Ciena: Blue Planet RA
Ciena: Blue Planet SOO
Ciena: Blue Planet BPMN
Ciena: Blue Planet TOSCA

We have moved the extensions behind our firewall.

[vaisriva]

Ownership:

[isidorn]

I suggest that you simple unpublish those extensoins from the marketplace in this case. Would that work?

[vaibhavcodegeek]

Thanks.. It worked :)

[kareem613]

Can an extension be deprecated and pointed to an extension in a publisher owned by a different user?
My scenario is our company go acquired and we need to move our extension over to another publisher that's owned by a different user.

Also, how long does it take from when we request deprecation to when it's applied.

[GitMensch]

Yes, that's possible and was often done in the past, including for all of "original forks" (then "upstream becomes read-only"), replacements (separate one is now developed) and "renames" (w/wo publisher change).

For deprecation: the "old" repo-owner should either come here or a link to an official announcement be posted by someone; in both cases there can be a suggested "use instead".

[haeun-p]

Please deprecate webOS TV in favor of webOS Studio.

[isidorn]

Can you prove that you are the owner of the first extension? Thank you

[haeun-p]

@isidorn
Is this enough to prove that I'm the owner of this extension?

Thanks in advance.

[isidorn]

Yes. I have just deprecated your extension. Should be propagated in the next couple of hours.
Thank you

[stan-at-work]

Please deprecate my extention:

This is the old one

remove-dart-error-imports

In favor of:

This is the new one

remove-dart-error-warning

---

Proof of ownership:

The old repo is on my github account (under the deprecate-v2 branch): https://github.com/stan-at-work/remove-dart-error-warning

The new extention is under the v5 branch: https://github.com/stan-at-work/remove-dart-error-warning/tree/v5

[isidorn]

Done. Thank you

[hoonoh]

Please deprecate Slonik Live Server, as it is no longer maintained. The repo is also archived.

[isidorn]

Done. Thank you

[nyncral]

Please deprecate dwm-git-simpleuse in favor of simple git

proof of ownership :

[isidorn]

Done. Thank you

[luispDesktop]

Hi, can you please deprecate our old extension.

Old one: Synopsys Code Sight
New one: Code Sight (Security)
Proof of ownership:

Thank you!

[KaporMirr]

Mrdko

[isidorn]

Done. Thank you

[ritwickdey]

[Not sure if it's correct place]

Why Live Server is removed without any notices? Bug? It was installed around 54M times

https://marketplace.visualstudio.com/items?itemName=ritwickdey.LiveServer

ritwickdey/vscode-live-server#3061

[isidorn]

Explained in ritwickdey/vscode-live-server#3061 and microsoft/vsmarketplace#1114

[nathanielCherian]

Hi, can you please deprecate our existing extension in favor of this new one?
Old extension: https://marketplace.visualstudio.com/items?itemName=NathanielCherian.cashscript
New extension: https://marketplace.visualstudio.com/items?itemName=CashScript.cashscript-vscode
Proof of Ownership:

Thanks!

[isidorn]

Done. Thank you

[mammothb]

Hi, can you please deprecate the following extension in favor of the new one?

Old: https://marketplace.visualstudio.com/items?itemName=mammothb.scilab
New: https://marketplace.visualstudio.com/items?itemName=mammothb.vscode-scilab-syntax

Proof of ownership:

[isidorn]

Done, thank you!

[mammothb]

Sorry, I might have misunderstood the effect of deprecation. Does this free up the "scible" identifier for others to use?

If not, is it possible to have the extension (https://marketplace.visualstudio.com/items?itemName=mammothb.scilab) removed instead? So that I can free up the "scilab" identifier for others to use

[isidorn]

For that you can unpublish the extension yourself. You should be able to do that from the Marketplace manage UI.

[mammothb]

I initially tried that but it didn't free up the "scilab" identifier for another author to create an extension using the "scilab" name

[isidorn]

It might be that we do not free it up due to security reasons.

[Lim-Watt]

Hi, can you please deprecate the following extension in favor of the new one?

Old: https://marketplace.visualstudio.com/items?itemName=ElectronicElementsStudio.txt-read-in-code
New: https://marketplace.visualstudio.com/items?itemName=Artitsy.txt-read-in-code-comments

Proof of ownership:

[isidorn]

Done, thank you!

[lifeart]

Hi, can you please deprecate the following extension in favor of the new one?

Old: https://marketplace.visualstudio.com/items?itemName=lifeart.vscode-ember-unstable
New: https://marketplace.visualstudio.com/items?itemName=EmberTooling.vscode-ember

Proof of lifeart org ownership:

[pranaygp]

Not sure where to report this but a use has cloned my extension as is and has listed it on the marketplace as their own

• My extension (https://marketplace.visualstudio.com/items?itemName=pranaygp.vscode-css-peek) - 6.6M installs - Released 12/1/2016
• Their extension (https://marketplace.visualstudio.com/items?itemName=baoxin.vscode-css-peek-bx) - 1.2K installs - Released 4/1/2024

What's the best way to deal with this

[GitMensch]

that's nothing related to deprecation... you may want to consider to include the single commit they officially added pranaygp/vscode-css-peek@master...baoxin:vscode-css-peek:master (it is so small that I'd not consider it copyrightable and it is in a repo with the same license), but in any case I'd suggest to get in contact with them using the email behind that commit

[GJMcGowan]

Hello! Please deprecate the following extension: https://marketplace.visualstudio.com/items?itemName=dataform.dataform

Proof of ownership (in as much as a screenshot can prove anything...)

[lehni]

Could you please deprecate the following extension in favour of the new one?

Old: https://marketplace.visualstudio.com/items?itemName=lehni.vscode-fix-checksums
New: https://marketplace.visualstudio.com/items?itemName=RimuruChan.vscode-fix-checksums-next

Thanks!