Suggestions for new extension wanted #2919
Replies: 7 comments 4 replies
-
|
Considering how many extensions are available and that new ones are published very often (especially with the increase of people using AI to generate the bulk of an extension), it is not easy to market your extension. For me an extension needs to fill a real need and be easily discoverable on the marketplace or other places where I might find useful extensions, so I think marketing is quite important for an extension to be adopted by a wider audience. Some tips are given here: Additionally, you can try and suggest one of your extensions to be featured in the marketplace at microsoft/vscode#141472. Looking at https://github.com/eridien/vscode-definition-stack/tree/master, I like the idea. Since I read a lot of other people's source code, it could be useful for me. Although I usually read it on GitHub, and don't check out the source locally. I might try it out if it's available as a web extension, if I ever bother with the vscode.dev environment. I'm not sure what features I would expect, but a side panel like that with multiple features that help explain the code when browsing unfamiliar code, would have my interest. I also noticed you don't provide the links to the VS Code Marketplace in your repo or place them at the bottom. I would suggest putting those in the intro at the top. Make a simple and clear case of what your extension does for a user, and provide them with easy navigation to install it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. Unfortunately you picked my first extension which
was a total flop. I deprecated it. It was too hard to understand. It had
no good "elevator pitch".
One of the two that gained a little traction was JSON Commenter which has
an obvious usage and filled a need. I'm retired and I am going to just
keep running them up the flagpole until someone waves.
…On Sun, Nov 23, 2025 at 1:10 AM Kevin Ramharak ***@***.***> wrote:
Considering how many extensions are available and that new ones are
published very often (especially with the increase of people using AI to
generate the bulk of an extension), it is not easy to market your extension.
For me an extension needs to fill a real need and be easily discoverable
on the marketplace or other places where I might find useful extensions, so
I think marketing is quite important for an extension to be adopted by a
wider audience.
Some tips are given here:
-
https://code.visualstudio.com/api/references/extension-manifest#marketplace-presentation-tips
Additionally, you can try and suggest one of your extensions to be
featured in the marketplace at microsoft/vscode#141472
<microsoft/vscode#141472>.
Looking at https://github.com/eridien/vscode-definition-stack/tree/master,
I like the idea. Since I read a lot of other people's source code, it could
be useful for me. Although I usually read it on GitHub, and don't check out
the source locally. I might try it out if it's available as a web
extension, if I ever bother with the vscode.dev environment.
I'm not sure what features I would expect, but a side panel like that with
multiple features that help explain the code when browsing unfamiliar code,
would have my interest.
I also noticed you don't provide the links to the VS Code Marketplace in
your repo or place them at the bottom. I would suggest putting those in the
intro at the top. Make a simple and clear case of what your extension does
for a user, and provide them with easy navigation to install it.
—
Reply to this email directly, view it on GitHub
<#2919 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGGDPZV6DBGSOJKGCBSVTT36F2Z3AVCNFSM6AAAAACM5D32F2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBVGE3DSMI>
.
You are receiving this because you authored the thread.Message ID:
<microsoft/vscode-discussions/repo-discussions/2919/comments/15051691@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
That is worth trying. As for me, I am also in a position where I have a lot of time, and thus am dabbling in extension development myself. Even if it doesn't amount to much traction, I am learning an amazing amount of things. You could consider looking at other extensions that you find useful but lacking in areas, and see if you can submit some PR's there. That is how I got involved with https://github.com/yoavbls/pretty-ts-errors. Another extension I'm working on is about regex discovery and tooling in a project, which mostly came from an actual need I had while working on that repo. So any need you see in your own workflows, where an extension would really help can inspire an idea. I noticed you used tree-sitter in one of your extensions. One idea that comes to mind is a better playground implementation of https://marketplace.visualstudio.com/items?itemName=jrieken.vscode-tree-sitter-query. I use tree sitter in a project, and while both that extension and the playground at https://tree-sitter.github.io/tree-sitter/7-playground.html are very helpful, I would really like a better and up to date implementation that has the features of both and is a bit more robust (see the open issues of the vscode extension). It also introduced me to the power of the Notebook feature of VS Code. I think extensions that fill the gap between an external tool and my workflow inside VS Code are mostly what I am looking for. Based on some of the work and research I have done Tree Sitter is going to be the de facto syntax highlighter engine for VS Code and other editors, and probably power a lot more tools outside of it. Good developer tooling is still a bit lacking, as far as I can tell. I think there are a lot of very useful tools, that add value to developers and software projects, but are just too much of a pain to integrate or configure. Maybe in some other area you find interesting, you can see prototype how to bring the value of those tools into developer workflows, without it becoming a configuration nightmare. I would suggest trying to avoid fully custom webviews, because while they are very powerful, the UI sticks out like a sore thumb in VS Code. I think using as much VS Code UI elements as possible will make it a lot easier for the end user to integrate in their workflow. Notebooks could be one of those integrated UI elements, that still gives a lot of room for custom UI implementations, yet also looks and feels native. I hope that gives some direction in where you could go. I think it's pretty cool that you are still coding when retired, definitely where I hope to end up in my retirement. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the advice.
…On Sun, Nov 23, 2025 at 11:04 AM Kevin Ramharak ***@***.***> wrote:
That is worth trying. As for me, I am also in a position where I have a
lot of time, and thus am dabbling in extension development myself. Even if
it doesn't amount to much traction, I am learning an amazing amount of
things.
You could consider looking at other extensions that you find useful but
lacking in areas, and see if you can submit some PR's there. That is how I
got involved with https://github.com/yoavbls/pretty-ts-errors.
Another extension I'm working on is about regex discovery and tooling in a
project, which mostly came from an actual need I had while working on that
repo. So any need you see in your own workflows, where an extension would
really help can inspire an idea.
I noticed you used tree-sitter in one of your extensions. One idea that
comes to mind is a better playground implementation of
https://marketplace.visualstudio.com/items?itemName=jrieken.vscode-tree-sitter-query.
I use tree sitter in a project, and while both that extension and the
playground at https://tree-sitter.github.io/tree-sitter/7-playground.html
are very helpful, I would really like a better and up to date
implementation that has the features of both and is a bit more robust (see
the open issues of the vscode extension).
It also introduced me to the power of the Notebook
<https://code.visualstudio.com/blogs/2021/11/08/custom-notebooks> feature
of VS Code. I think extensions that fill the gap between an external tool
and my workflow inside VS Code are mostly what I am looking for. Based on
some of the work and research I have done Tree Sitter is going to be the de
facto syntax highlighter engine for VS Code and other editors, and probably
power a lot more tools outside of it. Good developer tooling is still a bit
lacking, as far as I can tell.
I think there are a lot of very useful tools, that add value to developers
and software projects, but are just too much of a pain to integrate or
configure. Maybe in some other area you find interesting, you can see
prototype how to bring the value of those tools into developer workflows,
without it becoming a configuration nightmare. I would suggest trying to
avoid fully custom webviews, because while they are very powerful, the UI
sticks out like a sore thumb in VS Code. I think using as much VS Code UI
elements as possible will make it a lot easier for the end user to
integrate in their workflow. Notebooks could be one of those integrated UI
elements, that still gives a lot of room for custom UI implementations, yet
also looks and feels native.
I hope that gives some direction in where you could go. I think it's
pretty cool that you are still coding when retired, definitely where I hope
to end up in my retirement.
—
Reply to this email directly, view it on GitHub
<#2919 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGGDPYWKB4PRWRGWHBGGKT36IAMPAVCNFSM6AAAAACM5D32F2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBVGQ2DCMQ>
.
You are receiving this because you authored the thread.Message ID:
<microsoft/vscode-discussions/repo-discussions/2919/comments/15054412@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @mark-hahn , If you are looking for extension ideas that may have good traction, maybe you could look for feature requests at the VS Code repo, using two different approaches:
Talking about myself, most of the extensions I developed and maintain were created to fulfill three desires: fulfill my needs, learn and provide feedback. Either because it was something that I missed in VS Code at the moment, like Bookmarks and Project Manager; because it was clear it wouldn't be part of its core, like the Delphi/Pascal related ones; or simply because I wanna explore some VS Code API that weren't suitable in any of my other extensions. But, one of them was created using exactly the approach I suggested above, and also because I was looking for some new API to learn and play with. Then I created the Separators extension, based on this request this VS Code issue. Also, if you look here, in this discussions forum, you may find some requests for new extensions as well. Maybe some of it fits you. Let us know your new adventures 😬 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the excellent ideas. I have only worked on things that I wanted to use. Although I have often found that the weren't useful after I've finished them. There wasn't any way to know until I had it in my toolbox. Out of the five or so extensions I've developed there are only two I've used regularly. If you don't mind, I have some personal questions. I'm trying to get a picture of how a successful developer works on extensions. How many hours a week do you spend on extensions? Do you do this outside work or is this part of a paying job? Do you make any money from them? How long have you been doing this? Are you using AI yet? I would totally understand if you tell me to mind my own business. |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone know of a css/style manager that lets you refactor css and move
it between inline and in blocks? I am often guilty of using inline css
excessively and duplicated. It could suggest refactoring. It could work
with separate files or single-file-components in vue.
…On Sun, Nov 30, 2025 at 12:14 PM Mark Hahn ***@***.***> wrote:
Thanks for the excellent ideas. I have only worked on things that I wanted
to use. Although I have often found that the weren't useful after I've
finished them. There wasn't any way to know until I had it in my toolbox.
Out of the five or so extensions I've developed there are only two I've
used regularly.
If you don't mind, I have some personal questions. I'm trying to get a
picture of how a successful developer works on extensions.
How many hours a week do you spend on extensions? Do you do this outside
work or is this part of a paying job? Do you make any money from them? How
long have you been doing this? Are you using AI yet?
I would totally understand if you tell me to mind my own business.
—
Reply to this email directly, view it on GitHub
<#2919 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGGDPYYLX5Y2L2NJU4OUVT37NFZ3AVCNFSM6AAAAACM5D32F2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJRHA2DCMI>
.
You are receiving this because you are subscribed to this thread.Message
ID: <microsoft/vscode-discussions/repo-discussions/2919/comments/15118411@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @mark-hahn , I'm not working with CSS for a while, so I don't have a quick answer for that, but either way, I guess you could also play with GitHub Copilot for some ideas of missing extensions as well, using a prompt like this: 
Hope this helps |
Beta Was this translation helpful? Give feedback.
-
|
I guess I'll give up on trying to do an extension and switch to personal
projects. AI has killed any reason.
1) Anyone can create any extension they can think of. My last one took 2
to 3 days and I never saw the code although it did take skill to guide the
AI.
2) You can replace the functionality of any transformational extension with
AI prompts.
3) Who needs to use an extension when you can just have AI create the app?
Vscode isn't even needed.
…On Mon, Dec 1, 2025 at 8:23 AM Alessandro Fragnani ***@***.***> wrote:
Hi @mark-hahn <https://github.com/mark-hahn> ,
I'm not working with CSS for a while, so I don't have a quick answer for
that, but either way, I guess you could also play with GitHub Copilot for
some *ideas of missing extensions* as well, using a prompt like this:
image.png (view on web)
<https://github.com/user-attachments/assets/b39f4a07-cc2f-48a0-a6aa-d2081b6345a1>
Hope this helps
—
Reply to this email directly, view it on GitHub
<#2919 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGGDP67SZH2EFN4ZHQ633337RTQLAVCNFSM6AAAAACM5D32F2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJSGYZDCOI>
.
You are receiving this because you were mentioned.Message ID:
<microsoft/vscode-discussions/repo-discussions/2919/comments/15126219@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I wouldn't give up on creating extensions, simply because I don't think AI killed anything. I mean, anyone can indeed create an extension, for sure, but this is true since VS Code was launched 10 years ago. Today, AI just helps you, as in any other area/tool/language. Creating an extension, with or without AI, still requires will, persistence, knowledge and time. AI won't give you that for free. You are in control, and you must tell it what you want. Number 2, on the other hand, I agree more. Up until now, any transformation I needed was possible using the basic GitHub Copilot install. But I still think some transformations would require more specialized tools like MCPs and Chat Participants, which then, may be developed using extensions. Number 3, on the other hand, I don't think so. I mean, we see a new VS Code fork being launched almost every month. So, VS Code is more required than never 😆 . For instance, if you see yourself replacing an extension idea with prompts, maybe you could create an extension that exposes those prompts. If you have specialized agents, try playing with chat participants. AI didn't kill anything, it just opened the toolbox for new kind of tools. |
Beta Was this translation helpful? Give feedback.
-
|
Today, AI just helps you, as in any other area/tool/language.
I would have agreed with you until recently. For the past year I found
copilot useful when venturing into unknown territory like using a new ast
parser. I would have it start with some task using the parser. Then I
would read and use the code to get a general understanding. Then as I
programmed I would ask questions about details instead of going to google
or reading the manual.
On my last project I started development by describing the extension and
asking copilot to scaffold it. To my surprise it gave me the working
extension with most of the features. It even had features I was planning on
but not described. It was kind of spooky. Then before even looking at the
code I described more features and once again I got even more than I
requested. I just went with the flow and before I knew it I had the
complete extension without seeing any code. It was embarrassing that I was
reduced to a vibe coder.
There was a major difference from previous AI usage. It got good enough at
discussing what was going on that I knew what algorithms it was using and
even some coding details and we would discuss different approaches. It
took me a few days to develop in what would have been a few weeks.
I have been programming for 60 yrs. I went from plugging jacks into a
board, to putting in numbers with switches, to putting in asm with cards,
to putting fortran in with cards, to using C with a terminal, to using
Basic with a "Home Computer", to using Java on a workstation, to using
Javascript. Not one of those advances compare to this latest shift. I'm
glad I'm retired and not counting on a programming paycheck.
Sorry for babbling.
…On Mon, Dec 1, 2025 at 1:50 PM Alessandro Fragnani ***@***.***> wrote:
I wouldn't give up on creating extensions, simply because I don't think AI
killed anything.
I mean, anyone can indeed create an extension, for sure, but this is true
since VS Code was launched 10 years ago. Today, AI just helps you, as in
any other area/tool/language. Creating an extension, with or without AI,
still requires *will, persistence, knowledge and time*. AI won't give you
that for free. You are in control, and you must tell it what you want.
Number 2, on the other hand, I agree more. Up until now, any
transformation *I needed* was possible using the basic GitHub Copilot
install. But I still think *some* transformations would require more
specialized tools like MCPs and Chat Participants, which then, may be
developed using extensions.
Number 3, on the other hand, I don't think so. I mean, we see a new VS
Code fork being launched almost every month. So, VS Code is more required
than never 😆 .
For instance, if you see yourself replacing an extension idea with
prompts, maybe you could create an extension that *exposes* those
prompts. If you have specialized agents, try playing with chat participants.
AI didn't kill anything, it just opened the toolbox for new kind of tools.
—
Reply to this email directly, view it on GitHub
<#2919 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGGDP26PC6LWQ77RAF4UIL37SZ2TAVCNFSM6AAAAACM5D32F2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJSHA4TONI>
.
You are receiving this because you were mentioned.Message ID:
<microsoft/vscode-discussions/repo-discussions/2919/comments/15128975@
github.com>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have developed three extensions of which none have generated any real interest. Can someone suggest an extension that they would like to have that doesn't exist?
Beta Was this translation helpful? Give feedback.
All reactions