I'm stuck on the point where my #neovim config regularly breaks whenever I do an #lazyvim (package manager) update.

[bender@mammut.moe]

I'm stuck on the point where my #neovim config regularly breaks whenever I do an #lazyvim (package manager) update. I'm aware about the lockfile and restore functionality, HOWEVER, I would really appreciate if people share their way to keeping their neovim sane and in working state , so please ↓

[abeestrada@mastodon.social]

@bender my strategy is using the nightly 0.12 vim.pack and keeping my plugins to a minimum

dotfiles/nvim/init.lua at master · AbeEstrada/dotfiles

My dotfiles. Contribute to AbeEstrada/dotfiles development by creating an account on GitHub.

GitHub (github.com)

[gemelen@mammut.moe]

@bender
If you're looking for a solution: in what way does your config breaks? I mean, there are plugins' breaking changes that are announced (or not) by the plugin manager for example; and there are config design decisions made that do not account for the changes from outside.

In my case, it's rarely breaks on updates in last few years due to the:
- I put some effort to reduce amount of plugins I use
- I use quite stable plugins (and some that are somewhat complete)
- I try to move to core features of the neovim as soon as they replace a plugin's functionality to the point it works for me
- and maybe some bits on the least required features surface

[bender@mammut.moe]

@gemelen frankly, I had a hard time migrating to 0.11. Maybe I just didn't pay enough credit to various plugin breaking changes, which is totally my fault. Currently I'm researching a distro #LazyVim, hoping they did a better job manag8ngvthr defaults than me, ha