vscode-vsce
publish-vscode-extension
Our great sponsors
vscode-vsce | publish-vscode-extension | |
---|---|---|
3 | 3 | |
752 | 192 | |
4.0% | - | |
8.5 | 6.8 | |
11 days ago | 25 days ago | |
TypeScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
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-vsce
-
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.
-
I automated publishing my VSCode Extension
I'm using VSCE - VSCode Extension Manager package to build and deploy my project to the Marketplace.
-
Write a VS Code extension in JavaScript, not TypeScript ^
There is a CLI tool called vsce for packaging and publishing extensions. It's easy to use. This will create a vsix package that can be installed as an extension.
publish-vscode-extension
-
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?
openvsx - An open-source registry for VS Code extensions
tabout - Tab out of quotes, brackets, etc for Visual Studio Code
vscode-extension-samples - Sample code illustrating the VS Code extension API.
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
vscode-snippets-ranger - View and edit all of your snippets in one purty place! Yee-haw!!
flatpak-vscode - Integrate Flatpak with VSCode
vscode-marky-stats - Configurable statistics of your markdown document on your status bar.
publish-extensions - Scripts for publishing VS Code extensions to open-vsx.org
release-action - An action which manages a github release
vscode-marquee - 💡 The missing VS Code homescreen that helps you to stay organized with minimal context switches