platformio-vscode-ide
publish-extensions
platformio-vscode-ide | publish-extensions | |
---|---|---|
8 | 8 | |
1,153 | 221 | |
1.7% | - | |
7.3 | 8.3 | |
3 months ago | 1 day ago | |
JavaScript | JavaScript | |
Apache License 2.0 | 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.
platformio-vscode-ide
-
VSCodium – Free/Libre Open Source Software Binaries of VS Code
There is a workaround for PlatformIO that I use to get it to work in VSCodium: https://github.com/platformio/platformio-vscode-ide/issues/1...
-
Extensions are not automatically found within VS Code when using Arch Linux
The PlatformIO extension currently requires Microsoft's proprietary C/C++ extension, so it can't (officially) be used in the Arch community build. Here's a feature request to remove the dependency on the C/C++ extension: https://github.com/platformio/platformio-vscode-ide/issues/1802
-
Extensions not showing up in the marketplace? Arch Linux
There is an open issue on their repo, it seems the ms-vscode.cpptools extension which it depends on isn't open source so it can't be published on Open VSX (the marketplace used by OSS builds of VSCode) until they manage to use the open source alternative as a replacement llvm-vs-code-extensions.vscode-clangd
- Firmware cannot compile. Was working earlier yesterday but now nothing works
-
Help with firmware troubles!!!
You might be experiencing a problem that has plagued a lot of people, which is explained in the GitHub issue report. If this is indeed the problem, there are workarounds for it. Good luck!
-
VS Code update 1.56 breaks PlatformIO compile and upload functionality
Thanks for the provided information. There is a reported issue https://github.com/platformio/platformio-vscode-ide/issues/2554 and we work on reproducing. Please follow issue #2554.
-
PIO Home server won't start | Where is the 'PlatformIO IDE Terminal'?
I'm trying to install platformio on vscode, but I keep getting this error: Could not start PIO Home server: Error: timeout . It leads you this github page where you are prompted to open the PlatformIO IDE Terminal, but no matter which terminal I open (powershell, cmd, bash) the command is not recognised. What should I do?
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?
BIGTREETECH-SKR-mini-E3 - BIGTREETECH SKR-mini-E3 motherboard is a ultra-quiet, low-power, high-quality 3D printing machine control board. It is launched by the 3D printing team of Shenzhen BIGTREE technology co., LTD. This board is specially tailored for Ender 3 printer, perfectly replacing the original Ender3 printer motherboard.
openvsx - An open-source registry for VS Code extensions
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
picovoice - On-device voice assistant platform powered by deep learning
open-vsx.org - Source of open-vsx.org
icestudio - :snowflake: Visual editor for open FPGA boards
omnisharp-vscode - Official C# support for Visual Studio Code [Moved to: https://github.com/dotnet/vscode-csharp]
pigpio - pigpio is a C library for the Raspberry which allows control of the General Purpose Input Outputs (GPIO).
Code-Server - VS Code in the browser
johnny-five - JavaScript Robotics and IoT programming framework, developed at Bocoup.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.