You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When lazy.nvim loads for the first time, it does not use the lock file. It may install the latest updates of plugins with breaking changes.
Even though :Lazy restore command can be used to restore plugin versions from the lock file, it is very troublesome. Sometimes plugins may even break the Neovim UI. This makes it harder to restore plugin versions.
If there was an option in lazy.nvim configuration, something like prefer_lock_file = true, then it would improve the user experience of both lazy.nvim and Neovim. This would improve setting up Neovim on a new machine or on multiple machines.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When lazy.nvim loads for the first time, it does not use the lock file. It may install the latest updates of plugins with breaking changes.
Even though
:Lazy restore
command can be used to restore plugin versions from the lock file, it is very troublesome. Sometimes plugins may even break the Neovim UI. This makes it harder to restore plugin versions.If there was an option in lazy.nvim configuration, something like
prefer_lock_file = true
, then it would improve the user experience of both lazy.nvim and Neovim. This would improve setting up Neovim on a new machine or on multiple machines.Is there any way to achieve this behavior?
Beta Was this translation helpful? Give feedback.
All reactions