Our great sponsors
-
packer.nvim
A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
My usual advice here is: - Use paq if you want a minimalist plugin manager that does less for you but is simpler to use - Use packer if you want more features (mostly a bunch of options for lazy-loading, Luarocks integration, integrated profiling, maybe a few smaller things I'm not thinking of) and don't mind a slight learning curve at the start (though https://github.com/wbthomason/packer.nvim/pull/402, when it happens, should get rid of a lot of this learning curve) - Use vim-plug (or dein, etc.) if it works for you and you're happy with it
I am prone to start testing paq-nvim as first option, but I'd be glad to receive feedback about either one.
And then, vim-plug, which is also from the author of the beloved fzf; vim-plug is arguably the more mature one, and the experience to configure it in lua isn't that bad, here's is mine for example.
Thank you. I see that LunarVim adopted packer.