vscode-marky-stats
Configurable statistics of your markdown document on your status bar. (by robole)
publish-vscode-extension
GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace. (by HaaLeo)
Our great sponsors
| vscode-marky-stats | publish-vscode-extension | |
|---|---|---|
| 1 | 3 | |
| 7 | 192 | |
| - | - | |
| 2.9 | 6.8 | |
| about 1 year ago | 22 days ago | |
| JavaScript | TypeScript | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-marky-stats
Posts with mentions or reviews of vscode-marky-stats.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-06-16.
-
Write a VS Code extension in JavaScript, not TypeScript ^
Like any JavaScript project, you can use any bundler you wish. Bundling can make even an extension with just a few modules load considerably faster. I looked at this with Marky Stats which has 3 short modules, and it improved the loading time. This is optimization, if you are beginner, do not feel obligated to do it. Pace yourself!
publish-vscode-extension
Posts with mentions or reviews of publish-vscode-extension.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-31.
-
VS Code or VS Codium - Which should I use?
I have written a number of extensions, and I use the publish-vscode-extension GitHub action to publish my extensions to both marketplaces.
-
GitHub Action You Need to Publish VS Code Extensions
Lastly we will package and publish our extension using the Visual Studio Code Extension Manager and a GitHub Action called HaaLeo/publish-vscode-extension. The advantage of having the packaging and publishing step separated is that we can attach the compiled .vsix file as an artifact to the workflow and offer it as download. Make sure to generate a token (named in the workflow as VSC_MKTP_PAT and OPEN_VSX_TOKEN) to allow GitHub to publish your extension.
-
Write a VS Code extension in JavaScript, not TypeScript ^
I use this github action to automate publishing of an extension to both marketplaces, publication is triggered when the main branch is updated. There a couple of other github actions for
What are some alternatives?
When comparing vscode-marky-stats and publish-vscode-extension you can also consider the following projects:
AutoIt-VSCode - AutoIt Extension for Visual Studio Code
tabout - Tab out of quotes, brackets, etc for Visual Studio Code
vscode-vsce - VS Code Extension Manager
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
openvsx - An open-source registry for VS Code extensions
vscode-extension-samples - Sample code illustrating the VS Code extension API.
flatpak-vscode - Integrate Flatpak with VSCode
vscode-snippets-ranger - View and edit all of your snippets in one purty place! Yee-haw!!
publish-extensions - Scripts for publishing VS Code extensions to open-vsx.org
release-action - An action which manages a github release
vscode-marky-stats vs AutoIt-VSCode
publish-vscode-extension vs tabout
vscode-marky-stats vs vscode-vsce
publish-vscode-extension vs vscode-git-graph
vscode-marky-stats vs openvsx
publish-vscode-extension vs vscode-vsce
vscode-marky-stats vs vscode-extension-samples
publish-vscode-extension vs flatpak-vscode
vscode-marky-stats vs vscode-snippets-ranger
publish-vscode-extension vs publish-extensions
publish-vscode-extension vs vscode-extension-samples
publish-vscode-extension vs release-action