Background I’ve been using the excellent lazy.nvim package manager for more than three years now, and I’ve been super happy with it. But with Neovim v0.12.0, vim.pack was shipped: a built-in (but still experimental) plugin manager that manages plugins using Git, with no third-party dependencies required, implemented by Evgeni Chasnovski (see neovim/neovim#34009), known for his work on mini.nvim. This piqued my interest, as I’ve found myself creating abstractions and isolations with lazy.nvim that don’t harmonize with my grug brain. So I figured I wanted to see if I could simplify by moving onto vim.pack.
  • SinTan1729@programming.devEnglish
    1·
    19 days ago

    I decided to migrate to zpack.nvim instead. Got to keep my old lazy config with minimal changes, and it works pretty great. I guess I just like the modular nature of my setup, and also I just went through a major rewrite last month, don’t wanna redo it just yet.