flake-parts
nvfetcher
Our great sponsors
flake-parts | nvfetcher | |
---|---|---|
5 | 6 | |
586 | 149 | |
9.0% | - | |
7.5 | 5.9 | |
14 days ago | 12 days ago | |
Nix | Haskell | |
MIT License | 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.
flake-parts
-
Nix is a better Docker image builder than Docker's image builder
There are attempts like
https://flake.parts/
or
https://github.com/nix-community/flakelight
Their aim is to create an ecosystem of reusable Nix libraries. But it is tiny.
-
Nix noob question
You can also just install flakes doing nix profile install . I wrote a tool to make it a bit easier, npt but it's completely optional. Once you install the packages with nix profile. Then in your repos you can use a flake with a devShell and run nix develop. Check https://flake.parts to write your flakes.
-
I'm getting on the hype train. What do you recommend to beginner?
Definitely use flakes from the get-go. It's much more sane. Nix's documentation can be unorganized, but read through it when you can. Modules and other projects tend to have their own documentation as well, like Home Manager and flake-parts
-
Why you don't need flake-utils
That's not a typo, there OP is referring to https://github.com/hercules-ci/flake-parts
nvfetcher
-
Why you don't need flake-utils
Pinning can be done without flakes, be it manually or with codegen (nvfetcher)
-
Accessing contents of non-flake repo input to a flake?
You should instead use the regular fetchGit, fetchFromGitHub etc. fetchers in fairly vanilla code, and yes, that often means dealing with checksums in some form. If you truly just want to yeet the latest revision into place no matter what it is, there are ways to automate that still, such as berberman/nvfetcher, or Mic92/nix-update.
-
Will you move from Packer to Lazy ?
Yes, however one downside is that, afaik, the inputs are downloaded eagerly, not lazily. Alternatively there are things like nix-update and nvfetcher.
-
Nix VSCode Marketplace
The fetcher for this is https://github.com/berberman/nvfetcher. And if you want to simply map all the sources to extension packes, you could use http://github.com/divnix/devos-ext-lib and follow the readme. This is how I do it.
-
Nix flake of Vim/Neovim plugins, part of them are auto-generated from Awesome Neovim
It has support for passthru so you can expose description, homepage and other meta attributes. You (currently) can't directly pass a attribute set to the nix source because nvfetcher is using string interpolation to generate it, so only string is allowed. There is a tracking issue for this: github.com/berberman/nvfetcher/issues/40. For now, you can use mapAttrs sources (sources = import ./_sources/generated.nix { inherit (final) fetchurl fetchgit fetchFromGitHub; }) to generate the appropriate meta from passthru.
What are some alternatives?
nix-beam-flakes - Nix-based BEAM toolchain management
flake-awesome-neovim-plugins - Nix flake of Awesome Neovim plugins
dev-templates - Dev environments for numerous languages based on Nix flakes [maintainer=@lucperkins]
openvsx - An open-source registry for VS Code extensions
treefmt-nix - treefmt nix configuration
devos-ext-lib - A kick ass library to dominate your Extensions (with DevOS).
haumea - Filesystem-based module system for Nix [maintainer=@figsoda]
LazyVim - Neovim config for the lazy
nixt - Simple unit-testing for Nix [maintainer=@Lord-Valen]
nixos-configuration
Nix-Config - My Nix Config
commander-cli - A simple library I wrote to allow me to quickly and easily construct command line interfaces.