12.nixvim/modules/top-level
Austin Horstman cbd8536a05
Some checks failed
Publish every Git push to main to FlakeHub / flakehub-publish (push) Has been cancelled
Publish every git push to Flakestry / publish-flake (push) Has been cancelled
Documentation / Version info (push) Has been cancelled
Documentation / Build (push) Has been cancelled
Documentation / Combine builds (push) Has been cancelled
Documentation / Deploy (push) Has been cancelled
modules/output: restore plugin lua dependencies
With the newer nixpkgs Neovim wrapper, plugin Lua dependencies are surfaced through neovimUtils.makeVimPackageInfo as vimPackageInfo.luaDependencies. Nixvim was still only feeding explicit extraLuaPackages into its wrapper Lua environment, so plugin-provided Lua modules stopped reaching the runtime search path after the flake.lock bump.

That showed up as real runtime failures: Telescope could not load plenary.strings and Neorg could not load lua-utils, even though explicit extraLuaPackages still worked.

Fix that by computing vimPackageInfo from config.build.plugins and appending vimPackageInfo.luaDependencies to the wrapper's extraLuaPackages. That keeps Nixvim aligned with the nixpkgs/Home Manager dependency resolution path instead of maintaining a separate recursive Lua dependency collector.

Add focused regression coverage for the two reported plugin cases:
- telescope -> plenary.strings
- neorg -> lua-utils
2026-03-29 16:40:02 +00:00
..
files treewide: apply linter suggestions 2025-12-28 04:26:49 +00:00
plugins treewide: apply linter suggestions 2025-12-28 04:26:49 +00:00
default.nix modules: refactor plugins code in top-level 2025-04-01 15:43:26 +02:00
nixpkgs.nix docs: use official names of NixOS, Home Manager and nix-darwin 2025-10-18 00:05:26 +00:00
output.nix modules/output: restore plugin lua dependencies 2026-03-29 16:40:02 +00:00
readonly-renames.nix treewide: apply linter suggestions 2025-12-28 04:26:49 +00:00
test.nix treewide: apply linter suggestions 2025-12-28 04:26:49 +00:00