publish-extensions
Atom
publish-extensions | Atom | |
---|---|---|
8 | 284 | |
221 | 58,803 | |
- | - | |
8.3 | 8.1 | |
1 day ago | over 1 year ago | |
JavaScript | JavaScript | |
Eclipse Public License 2.0 | 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-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.
Atom
-
Is downloading vs code okay in this case ?
For JavaScript, HTML, and CSS, Visual Studio Code is the best solution because it already runs on the Electron framework. So, try VSCode. Don't worry; your device won't be harmed. If its performance was unbearable, you can always put it aside. You can also try Atom. It is outdated, but it could be answer to your need.
-
I am having an issue
you can still get atom from it github page: https://github.com/atom/atom/releases/tag/v1.60.0
- Dev environment for scripting?
-
Ask HN: Design of Emacs type extensible editor based on electron?
I'm surprised that nobody here mentioned Atom [1]. IIUC, Atom was designed to be hackable like Emacs.
A successor to Atom is Pulsar [2].
[1] https://github.com/atom/atom
[2] https://pulsar-edit.dev/
-
App LIST!!!
atom (RIP buddy! Free) Atom is a hackable text editor for the 21st century, built on Electron, and based on everything we love about our favourite editors. We designed it to be deeply customizable, but still approachable using the default configuration
- I started a course by Dr Angela Yu and one of the CSS courses tell me to download Atom.io. However, there is no way to download it anymore. I'm going crazy, can someone please help??
-
Code Editor from scratch ?
Hey everyone, I'm developing an open source text editor called Valence. I'm just getting started with its development and the next and main thing I need to implement is the editor itself. Now I know there are many different code editors like CodeMirror, Ace.js and Monaco but I want to start from scratch and build something like Atom had done. Currently I created a contenteditable div and also added a custom cursor. BTW I'm using React, TailwindCSS and TypeScript. Here is the component
-
I've been using Atom to edit code, and then this popped up today. Anybody know the story behind this? (using a Macbook with BigSure OS installed)
These versions of Atom will stop working on February 2 [2023]. To keep using Atom, users will need to download a previous Atom version.
-
" “Atom” will damage your computer. You should move it to the Trash.“Atom” will damage your computer. You should move it to the Trash. "
For Mac users - mv ~/.atom ~/atom_bak rm -fr /Applications/Atom.app download https://github.com/atom/atom/releases/tag/v1.60.0 Drag download to Applications folder - to install
-
Can't install AUR atom
And it doesn't match because https://github.com/atom/atom/releases/download/v1.63.1/atom-amd64.deb returns a 404 not found error, so of course it doesn't match.
What are some alternatives?
openvsx - An open-source registry for VS Code extensions
Visual Studio Code - Visual Studio Code
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
Geany - A fast and lightweight IDE
open-vsx.org - Source of open-vsx.org
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
omnisharp-vscode - Official C# support for Visual Studio Code [Moved to: https://github.com/dotnet/vscode-csharp]
Spyder - Official repository for Spyder - The Scientific Python Development Environment
Code-Server - VS Code in the browser
notepad-plus-plus - Notepad++ official repository
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
KDevelop - Cross-platform IDE for C, C++, Python, QML/JavaScript and PHP