-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaking Change - New Plugin Manager: lazy.nvim #27
Comments
Cool :) |
Thanks :) |
Use lazy update here: https://github.com/brainfucksec/neovim-lua/blob/main/nvim/lua/plugins/alpha-nvim.lua#L46 Thanks for providing the awesome template. |
Hi i migrate. Everything is running fine. |
Thanks, I have already updated the indicated command, thanks again for highlighting it :) See: commit 8701098 |
As of today (Feb. 25, 2023)
lazy.nvim
is used as the plugin manager instead ofpacker
.See commit: 2db1c38
Details
Old package: packer.nvim
New package: lazy.nvim
Directories
Changing the plugin manager involves changing the directory structure of Neovim.
Old Neovim directory structure with
packer
:${HOME}/.config/nvim/
Files to be removed:
New Neovim directory structure with
lazy.nvim
:Note: Update the
init.lua
file with the instruction for load lazy configuration file:New lazy.nvim files:
The
lazy.lua
is the configuration file, is very similar topacker_init.lua
and makes it easy to migrate, see: https://github.com/folke/lazy.nvim#-migration-guideThe
lazy-lock.json
is automatically created when you runlazy.nvim
for the first time, is the file with the git package information of the installed plugins, see: https://github.com/folke/lazy.nvim#-lockfile-lazy-lockjsonInstalled plugins folder
The directory where the installed plugins are located will also change:
Old directory with
packer
:${HOME}/.local/share/nvim/site/pack/packer/
New directory with
lazy.nvim
:${HOME}/.local/share/nvim/lazy/
Advices
It is recommended to back up the current configuration with
packer.nvim
before doing the migration, in this way you have a fallback copy of a working Neovim configuration.e.g.:
Backup of Neovim config and plugins directory with
cp
:Backup with rsync:
Before using
lazy.nvim
you should read the information on how to do this, see: https://github.com/folke/lazy.nvimFor any questions and help you can comment on this section where I will try to help you with the migration (which is not difficult anyway). :)
The text was updated successfully, but these errors were encountered: