Repository navigation
v0.1.0
The first release of nvimx — a home-manager module that manages your Neovim plugins with Nix, driven by the same lazy.nvim-style Lua config you already write.
Highlights
- home-manager module (
nvimx.homeModules.nvimx) you embed in your own dotfiles flake. - Lua-driven locking —
nvimx-lockruns a headless Neovim that really evaluates your lazy.nvim spec, writes the plugin list toplugins.json, and pins every plugin inflake.lock. - Pure builds — network access happens only while locking. Builds just read the lock files, so evaluation needs no network and no
--impure. The same lock always yields the same result. - Plugins from GitHub, not nixpkgs — no manual hash management for plugins that nixpkgs does not carry.
- Bring your own Neovim — point
programs.nvimx.packageatpkgs.neovim-unwrapped, neovim-nightly-overlay, or anything else-unwrappedstyle. - Graceful degradation — switching before you have a lock does not fail; it builds a lazy.nvim-only Neovim, warns you, and still installs the
nvimx-lockcommand. - Systems:
x86_64-linuxandaarch64-darwin, each covered by its own CI workflow.
Getting started
inputs.nvimx.url = "github:myuron/nvimx/v0.1.0";Then add nvimx.homeModules.nvimx to your home-manager modules and set programs.nvimx.enable = true; with a lockDir. See the README for the full setup, all module options, and docs/architecture.md for the design.
Before your first switch, lock straight from the flake:
nix run github:myuron/nvimx/v0.1.0#lock -- --config ./nvim --out ./nvim/nvimx-lock