vscode-vsce VS vscode-marquee

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'm using VSCE - VSCode Extension Manager package to build and deploy my project to the Marketplace.

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.

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.

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.

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