Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.

3recommend
0warn against
Jan 10, 2026first mention
Sep 8, 2026latest mention
Nov 25 – Oct 26
Used forper-project plugin settingsneovim plugin manager

Why people recommend it

“I've moved back to lazy.nvim instead of vim.pack”

switched from vim.packon “Lisp in Vim (2019)”

“lazy.nvim, which is a (ragingly popular) plugin loader”

Show 1 more

“I moved from Packer to Lazy.nvim”

Caveats and dissent

No one in these comments warned against it.

Often compared with

All comments 7

“Doesn't lazy.nvim have some support for that?”

“I've moved back to lazy.nvim instead of vim.pack”

switched from vim.packon “Lisp in Vim (2019)”

“lazy.nvim, which is a (ragingly popular) plugin loader”

“The other myriad of options (keys, cmds, event) that lazy.nvim provides would require you to set up appropriate autocommands.”

“Ironically, this itself makes it not very suitable to be a part of Neovim”

Have a look here. This is incredible guide to the `vim.pack`. https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack.html

“I moved from Packer to Lazy.nvim”

Threads where it came up

Also written as Lazy.nvim. Data: lazy-nvim.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help