andev0x/nvimz: A minimalist, high-performance Neovim configuration optimized for Neovim 0.12+
A minimalist, high-performance Neovim configuration optimized for Neovim 0.12+
andev0x/nvimz: A minimalist, high-performance Neovim configuration optimized for Neovim 0.12+
A minimalist, high-performance Neovim configuration optimized for Neovim 0.12+
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.
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.
If the recent update of #Neovim to version 0 12 took you by surprice(just like me)
And you want to migrate to #vimpack
This post explained it very well
https://yeripratama.com/blog/migrating-from-lazynvim-to-vimpack/
I'm pretty sure it won't be my approach but
I think someone like the approach of the author of the post.