Skip to content

Releases

v0.2.0

Choose a tag to compare

@myuron myuron released this 21 Sep 09:08
12ff0e0

The second release of nvimx. v0.1.0 could lock a spec and build it; v0.2.0 is about everything that comes after the first lock — resolving version constraints for real, updating one plugin without touching the rest, building the plugins that need a build step, and pointing a plugin at a working tree on your disk.

Highlights

  • Version constraints are resolved for real. A version = "^1.2" is resolved with git ls-remote --tags and lazy.nvim's own lazy.manage.semver, so the semantics match what lazy would have picked. defaults.version — an opts key lazy only applies at git-operation time — is materialized into each eligible plugin at extraction, instead of being lost.
  • nvimx-lock --update [name...] re-resolves everything, or just the plugins you name. Without it, an existing pin is kept while the plugin's identity is unchanged.
  • nvimx-lock --import-lazy-lock migrates an existing lazy-lock.json, so you keep the revisions lazy.nvim had already pinned for you instead of jumping to whatever is current.
  • Plugins that need a build step. A shipped build registry builds a plugin from its locked source with a real recipe (blink.cmp's Rust binary among them), and plugins.overrides / plugins.nixpkgsFallback are the escape hatches for everything else. A build nvimx cannot run automatically is now warned about at lock time rather than silently skipped.
  • Local plugin development. devPlugins + devPath route a plugin to a working tree on your disk; a spec that writes dev = true or its own dir is picked up automatically and never gets a flake input.
  • extraLuaPackages puts luarocks packages on LUA_PATH / LUA_CPATH for plugins that need them.
  • treesitter.grammars installs grammars from nixpkgs — "all", or a list you name.
  • Non-GitHub sources are validated at lock time instead of failing later, and a table-form build = { "make", ":TSUpdate" } now expands to per-step kinds rather than collapsing to one placeholder.
  • A failing plugin no longer aborts the run: three failure paths that used to kill the whole lock now degrade to a warning.
  • stylua + luacheck run as part of nix fmt, and CI runs nix flake check and nix fmt -- --ci per system.

Upgrading

No configuration change is required. Your next nvimx-lock run rewrites plugins.json in three ways, all of them cosmetic to the build:

  • optional is gone. The field was always null.
  • A spec's own lazy.nvim entry is integrated with the synthetic lazy-nvim input instead of colliding with it.
  • localPlugins records only the name. Entries used to carry the directory lazy resolved on the machine that ran the lock — an absolute, often $HOME-bearing path, in a file you commit. Nothing ever read it (devPath decides where a local plugin loads from), so dropping it changes no resolved directory. A plugins.json committed before this release keeps its dir until the next re-lock, and is ignored either way.

One behavior change worth knowing: a plugin whose spec sets dir without dev is now treated as a local plugin, so it gets no flake input. That is what lazy does with it too.

Getting started

inputs.nvimx.url = "github:myuron/nvimx/v0.2.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 and 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.2.0#lock -- --config ./nvim --out ./nvim/nvimx-lock

Coming from lazy.nvim with a lazy-lock.json you want to keep:

nix run github:myuron/nvimx/v0.2.0#lock -- --config ./nvim --out ./nvim/nvimx-lock --import-lazy-lock

Systems: x86_64-linux and aarch64-darwin.

Full changelog: v0.1.0...v0.2.0

v0.1.0

Choose a tag to compare

@myuron myuron released this 28 Jul 09:58
4525b39

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-lock runs a headless Neovim that really evaluates your lazy.nvim spec, writes the plugin list to plugins.json, and pins every plugin in flake.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.package at pkgs.neovim-unwrapped, neovim-nightly-overlay, or anything else -unwrapped style.
  • 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-lock command.
  • Systems: x86_64-linux and aarch64-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