Document this as official extension in README

[BPScott]

This repo was originally published at https://marketplace.visualstudio.com/items?itemName=thibaudcolas.stylelint, but has since moved to https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint.

What's going to happen to the extension published in the thibaudcolas namespace? Shall it be deleted? Deletion is be a bit of short-term pain - people wondering where their extension went - for long term consolidation around stylelint.vscode-stylelint.

[ntwb]

It was originally published at https://marketplace.visualstudio.com/items?itemName=shinnn.stylelint and removed by the author (including the repo), the stylelint community has since adopted the extension, @thibaudcolas made that first version above available so that the extension continued to exist, and that repo has now moved to the @stylelint org.

So, yeah, not ideal, now that stylelint has moved the @thibaudcolas repo here I doubt we can update that extension to add a notice saying "Please use stylelint.vscode-stylelint` instead, we may have to just wait until the install count can indicate that it has become the canonical extension version...

[BPScott]

What could be done is make thibaudcolas.stylelint be an empty extension that acts as a extension pack that installs stylelint.vscode-stylelint.

But if feels like that just puts off the pain - at some point it'd be nice to try and reduce the number of stylelint plugins to reduce the change of people getting confused.

[ntwb]

Agreed, it would be great to have some of these extensions deprecated:

Pinging the following users regarding their extensions:

• @pqml https://marketplace.visualstudio.com/items?itemName=pqml.vscode-stylelint-format
• @CalvinHong https://marketplace.visualstudio.com/items?itemName=calvinhong.stylelint-fix
• @hisanshao https://marketplace.visualstudio.com/items?itemName=hisanshao.stylelint-mixins
• @hex-ci https://marketplace.visualstudio.com/items?itemName=hex-ci.stylelint-plus
• @daosro https://marketplace.visualstudio.com/items?itemName=Daosro.stylelint

Now that the @stylelint org community has taken over the previous extension by @shinnn and now is up to date with the latest stylelint v12, supports autofix, and soon will no longer include the stylelint dependency (will use project installed version) would you consider deprecating your extensions in favor of this extension?

I'd be happy to also add all of you as contributors here on @stylelint

Release Notes: https://github.com/stylelint/vscode-stylelint/releases

[pqml]

Oh this is good news!
I will deprecate my extension ASAP.

[BPScott]

Seems we had similar ideas - I poked @hex-ci earlier :) hex-ci/vscode-stylelint-plus#18

[pqml]

Sorry for the delay, I've just removed my extension and archived my github repo.

[thibaudcolas]

Sorry for the delay, I’ve also removed the extension I had temporarily published. It’s a bit unfortunate that vsce unpublish is all or nothing, there was no way to add any kind of deprecation message that I could see. The repository for the extension was the same as this one (we moved it here), so GitHub already redirects here.

The official extension already has the most downloads of all extensions, and it has a different logo so I think that will help it stand out.

If anything I’d suggest more people add a review to the extension over at https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint&ssr=false#review-details.

[seangwright]

I followed the shinnn extension, which I had been using, to the @thibaudcolas one. Then I saw the "missing from marketplace" warning in VS Code and did a search and found this one.

I knew I was on the right track when I saw this issue. Maybe you can keep it pinned to help confirm to others that this is the extension they've been looking for (reverse jedi mind trick)?

[zfwf]

Add one more to the list not mentioned above: stuartzhang.stylelint-stzhang

Hi @stuartZhang , you might want to consider contributing to this extension instead.

[jeddy3]

I knew I was on the right track when I saw this issue. Maybe you can keep it pinned to help confirm to others that this is the extension they've been looking for (reverse jedi mind trick)?

I think we can close this issue with some clear signposting in the README. We should clearly state somewhere prominent that this is the officially supported extension. Perhaps further down the page, we explain the historical fragmentation.

[adalinesimonian]

I think we can close this issue with some clear signposting in the README. We should clearly state somewhere prominent that this is the officially supported extension. Perhaps further down the page, we explain the historical fragmentation.

In #232, I've updated the tagline at the top of the readme to say that this is the official extension. However, I haven't added any writing about the fragmentation. Given that it's been several years, is that still necessary? I'm not that familiar with the extension's history beyond what's discussed in this issue.

[jeddy3]

The changes in #232 look good to me.

However, I haven't added any writing about the fragmentation. Given that it's been several years, is that still necessary?

I don't think it's something we can control and we're fine to close this issue now that #232 is merged.

This extension comes out top in searches for stylelint and has the most number of downloads.

---

Inncidently, you've done amazing work in #224 and #228. Thank you so much!

[adalinesimonian]

However, I haven't added any writing about the fragmentation. Given that it's been several years, is that still necessary?

I don't think it's something we can control and we're fine to close this issue now that #232 is merged.

Great, going to close this. 🎉

Inncidently, you've done amazing work in #224 and #228. Thank you so much!

Thanks! There's more where that came from. 😉