tabout
Tab out of quotes, brackets, etc for Visual Studio Code (by albertromkes)
publish-vscode-extension
GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace. (by HaaLeo)
tabout | publish-vscode-extension | |
---|---|---|
1 | 3 | |
123 | 217 | |
0.0% | 1.8% | |
0.0 | 5.9 | |
over 2 years ago | 24 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
tabout
Posts with mentions or reviews of tabout.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Tab out dollar signs visual code
You can manually edit one of the extension files to also include the $ symbols. See this issue in the GitHub repository.
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 tabout and publish-vscode-extension you can also consider the following projects:
prettier-vscode - Visual Studio Code extension for Prettier
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
edamagit - Magit for VSCode
vscode-vsce - VS Code Extension Manager
vscode-dash - Dash, Zeal and Velocity documentation integration in Visual Studio Code 🔎📖
publish-extensions - Scripts for publishing VS Code extensions to open-vsx.org