publish-vscode-extension
publish-extensions
publish-vscode-extension | publish-extensions | |
---|---|---|
3 | 8 | |
192 | 220 | |
- | - | |
6.8 | 8.3 | |
28 days ago | 21 days ago | |
TypeScript | JavaScript | |
MIT License | Eclipse Public License 2.0 |
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
publish-extensions
-
VS Code – What's the deal with the telemetry?
The biggest caveat would be to be aware of the default connexion to an alternative extension store, https://open-vsx.org, instead of Microsoft's own store, which does not have all the extensions the official store has. But that's less and less an issue, thanks to projects such as https://github.com/open-vsx/publish-extensions. In the worst case, I just manually `git clone`d the desired extension in my local extension folder. Nothing to complain about otherwise
-
VSCodium – Free/Libre Open Source Software Binaries of VS Code
Hey folks, Geoff here from Gitpod. Very please to see there continues to be interest in open (and FOSS) software development tooling. VSCodium uses the OpenVSX registry (which Gitpod folks created) because the VS Market place is proprietary and can only be connected to from offical Visual Studio branded products.
If you can't find an extension when using VSCodium then please send a pull-request to this repository https://github.com/open-vsx/publish-extensions with the identifier and that will help grow the ecosystem of open tooling.
ICMYI - We blogged more about this over at https://www.gitpod.io/blog/openvscode-server-launch, https://www.gitpod.io/blog/cloud-ide-history and https://www.gitpod.io/blog/open-vsx.
-
VS Code or VS Codium - Which should I use?
Create a pull request to this repository to have the @open-vsx service account publish the extensions for you. It appears that they run a batch job to keep them up-to-date.
-
How to code, build, and deploy from an iPad using Gitlab and Gitpod
Geoff here from Gitpod. Solid write up and overview here. Some minor clarifications and helpful pointers!
There’s a community WIP pull request open right now to add Gitea support.
The visual studio marketplace is proprietary (by design) and as such we created OpenVSX for the open source ecosystem then gifted it to the eclipse foundation. If you see something not in OpenVSX send the pull request here https://github.com/open-vsx/publish-extensions
And, finally, Open source communities are eligible for complimentary plan upgrades to unlimited hours. https://www.gitpod.io/blog/gitpod-for-opensource
-
Reflections on Software Development from Anywhere on an iPad
Send a PR to https://github.com/open-vsx/publish-extensions
> One goal of Open VSX is to have extension maintainers publish their extensions according to the documentation. However, you may be missing specific extensions that have not been published by their maintainers: either they are not willing to do it, or they haven't found time to do it, or simply they haven't heard about Open VSX yet. Though the preferred solution for such a situation is to convince the maintainers to start publishing themselves, you can add the extensions here to have them published by our CI workflow.
-
GitHub Codespaces is now available for everyone on GitHub Teams and GitHub Enterprise Cloud
👋🧡 Geoff from Gitpod here. Thanks for your support. OpenVSX was created by Gitpod/TypeFox and gifted to the Eclipse Foundation to resolve the problem that the Visual Studio Marketplace is proprietary. Extensions can be configured to automatically be published via sending a pull-request to https://github.com/open-vsx/publish-extensions
-
Settings Sync error
The auto-publishing of the extension is failing, due to a misconfiguration of versions in it's package.json.
-
FLOSS version of VSCode and the extensions gallery
My third point addresses the FLOSS extensions not yet available on Open VSX. These can usually be added fairly easily via open-vsx/publish-extensions, or by asking the extension author to publish to Open VSX themselves. I believe this mindset is the only way in which FLOSS distributions of VS Code can ever be a viable alternative to Visual Studio Code.
What are some alternatives?
tabout - Tab out of quotes, brackets, etc for Visual Studio Code
openvsx - An open-source registry for VS Code extensions
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
vscode-vsce - VS Code Extension Manager
open-vsx.org - Source of open-vsx.org
flatpak-vscode - Integrate Flatpak with VSCode
omnisharp-vscode - Official C# support for Visual Studio Code [Moved to: https://github.com/dotnet/vscode-csharp]
vscode-extension-samples - Sample code illustrating the VS Code extension API.
Code-Server - VS Code in the browser
release-action - An action which manages a github release
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.