Comment by mi_lk
15 hours ago
> - d21b8c949ad7 pack: add built-in plugin manager `vim.pack
Can someone try to sell me this over lazy.nvim? I asked Claude to convert lazy config to pack and I was not happy with it because how verbose it turned out
15 hours ago
> - d21b8c949ad7 pack: add built-in plugin manager `vim.pack
Can someone try to sell me this over lazy.nvim? I asked Claude to convert lazy config to pack and I was not happy with it because how verbose it turned out
Have a look here. This is incredible guide to the `vim.pack`.
https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack....
Yes, I basically gave my vim config along with this blog to Claude and it figured out 95% stuff on its own.
I'm assuming there will be something like lazy.nvim built on top of vim.pack. Some of the conventions might go away (ie constantly calling `.setup`).
> how verbose it turned out
Verbose? The new plugin manager's interface is literature just vim.pack.add({url}), not sure what is verbose about that
If you want to replicate the lazy features then it will get verbose. Even using a dedicated plugin for lazy loading it's not as tight as lazy.nvim.
You may argue that you don't need lazy loading, which is fine, but they're not 1-to-1 compatible.
I always thought Vim/Nvim already had a built-in package manager, git clone inside ~/.vim/pack/*/start, am I missing anything by not using a "real" package manager?
> I always thought Vim/Nvim already had a built-in package manager
They do; I used minpac [1] back in the day with Vim. And now Neovim has vim.pack.
Every so often, a movement to create Vim and Neovim configurations with zero (or minimal) 3rd party plugins becomes popular. This means no lazyvim as the package manager.
The lazyvim package manager has all the bells and whistles, especially lazy loading plugins, which reduces Neovim's startup time if you have dozens of plugins installed. My LazyVim [2] configuration has 35 plugins total but only 6 load at startup; startup time: 76ms. Plugins you don't use often aren't loaded unless necessary.
[1]: http://vimcasts.org/episodes/minpac/
[2]: https://www.lazyvim.org
I imagine you are left with manual dependencies, manual updates, and possibly without lazy loading or portable configuration. That stuff is not strictly necessary and may be easy to roll your own if you're very into it, but it's comfortable to have a standard.
Lazyloading is already present in Vim, it’s called autoload and most plugins I’ve seen use that feature
https://learnvimscriptthehardway.stevelosh.com/chapters/53.h...
Not really. That’s what I do.
It being built in sounds nice, although I have some lines in my config that automatically install lazy if it’s missing.
Tried to switch but found lazy.nvim better