vscode-vsce
vscode-marquee
Our great sponsors
vscode-vsce | vscode-marquee | |
---|---|---|
3 | 4 | |
752 | 97 | |
4.0% | - | |
8.5 | 5.9 | |
11 days ago | 4 months 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.
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?
openvsx - An open-source registry for VS Code extensions
vsc-memer - vscode extension for making memes inside your code
vscode-extension-samples - Sample code illustrating the VS Code extension API.
publish-vscode-extension - GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace.
release-action - An action which manages a github release
vscode-snippets-ranger - View and edit all of your snippets in one purty place! Yee-haw!!
vscode-react-javascript-snippets - Extension for React/Javascript snippets with search supporting ES7+ and babel features
vscode-marky-stats - Configurable statistics of your markdown document on your status bar.
vscode-extension-gdunit3 - Visual Studio Code Extension for GdUnit3
Code-Server - VS Code in the browser