publish-vscode-extension
vscode-marquee
Our great sponsors
publish-vscode-extension | vscode-marquee | |
---|---|---|
3 | 4 | |
192 | 97 | |
- | - | |
7.1 | 5.9 | |
21 days ago | 4 months ago | |
TypeScript | TypeScript | |
MIT License | 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.
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
vscode-marquee
-
Projects Coming to Life 🌈 Inside of VS Code - Marquee's Project Mode
This and the desire for better DX is what motivated us (at Stateful) to introduce relevant onboarding information readily into Marquee - the high-density information homescreen for VS Code. As of Marquee v3.2.0 the beta UX of 🚀 Project Mode is available to you.
-
GitHub Action You Need to Publish VS Code Extensions
The term continuous integration and continuous delivery (short CI/CD) is a common best practice for software developers, including the ones building VS Code extensions. With the VS Code update from last November users have now access to pre-releases that allow developers to ship regular updates and offer testing out the latest cutting edge features from their extension to receive early feedback. In this blog post we’d like to share how Stateful releases its Marquee extension to the VS Code Marketplace and OpenVSX Registry through GitHub Actions. You can find a full example in the Marquee repository, feel free to copy and adapt it for your own extension.
-
The Popular VS Code Homescreen is Now Open Source
Come find us either on GitHub, our community channels on Discord & Gitter, or through the in-Marquee feedback channels. Also take a look at the roadmap to see what's on Marquee's horizon.
sounds great! let us know if you have any feature requests: https://github.com/stateful/vscode-marquee/issues
What are some alternatives?
tabout - Tab out of quotes, brackets, etc for Visual Studio Code
vsc-memer - vscode extension for making memes inside your code
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
release-action - An action which manages a github release
vscode-vsce - VS Code Extension Manager
vscode-react-javascript-snippets - Extension for React/Javascript snippets with search supporting ES7+ and babel features
flatpak-vscode - Integrate Flatpak with VSCode
vscode-extension-gdunit3 - Visual Studio Code Extension for GdUnit3
publish-extensions - Scripts for publishing VS Code extensions to open-vsx.org
Code-Server - VS Code in the browser
vscode-extension-samples - Sample code illustrating the VS Code extension API.