publish-extensions
nixpkgs
publish-extensions | nixpkgs | |
---|---|---|
8 | 975 | |
221 | 15,753 | |
- | 2.8% | |
8.3 | 10.0 | |
about 23 hours ago | 1 day ago | |
JavaScript | Nix | |
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.
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
What are some alternatives?
openvsx - An open-source registry for VS Code extensions
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
open-vsx.org - Source of open-vsx.org
git-lfs - Git extension for versioning large files
omnisharp-vscode - Official C# support for Visual Studio Code [Moved to: https://github.com/dotnet/vscode-csharp]
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
Code-Server - VS Code in the browser
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.