A dead simple Nix flake template for creating and managing Neovim configurations with Nix.
kickstart-nix.nvim is a Nix flake template designed to help users create and manage Neovim configurations using Nix. It simplifies the process of migrating existing Neovim setups to Nix by providing a minimal, flexible foundation that handles plugin management and dependency resolution through Nix, while keeping configuration in Lua.
Neovim users who want to manage their editor configuration with Nix, particularly those new to Nix or looking for a simple, unopinionated starting point without complex DSLs.
Developers choose kickstart-nix.nvim for its simplicity and flexibility—it avoids the complexity of framework-based approaches, uses Nix for reliable dependency management, and allows easy customization with standard Lua configuration files.
❄️ A dead simple Nix flake template repository for Neovim derivations [maintainer=@mrcjkb]
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports both nixpkgs and flake inputs for plugins, allowing users to choose between stable packages or bleeding-edge versions, as described in the Features section.
Uses Neovim's native Lua config structure in the nvim/ directory, making migration from existing dotfiles straightforward and maintaining familiarity, per the Philosophy.
Generates a .luarc.json file automatically for Lua language server integration, providing IDE support for the Neovim API and all managed plugins, as highlighted in the Features.
Enables creating distinct Neovim packages with custom plugin sets and config filters using the mkNeovim function, offering flexibility for different workflows.
Relies on nixpkgs.wrapNeovimUnstable, which has an unstable signature and may break when nixpkgs inputs change, requiring manual fixes—a risk noted in the IMPORTANT warning.
Changes to Lua configs often require Nix derivation rebuilds for testing, unlike direct editing in ~/.config/nvim, slowing down the feedback loop despite workarounds like dev shells.
Requires understanding of Nix flakes and overlays for customization beyond basics, which can be daunting for users new to Nix, despite the project aiming for all levels.