nvim-plugin-management

To add a Neovim plugin with lazy.nvim, create a lua/plugins/<plugin-name>.lua module file and register its import in the lua/config/lazy.lua spec array. You then commit the changes and push them to both origin and sub remotes.

Removing a lazy.nvim plugin involves deleting its corresponding lua/plugins/*.lua module file and removing its import entry from the lua/config/lazy.lua spec array. You must then commit the modifications and push them to both origin and sub remotes.

Yes, you need to commit the lazy-lock.json file when modifying Neovim plugins if it is present. Committing this lockfile alongside your lua/plugins and lua/config/lazy.lua changes ensures consistent plugin versions across your machines.

Lazy-loading based on filetypes in lazy.nvim means plugins are only loaded when specific filetypes are opened. When adding plugins, you need to account for this ft-based lazy-loading behavior to ensure plugins activate correctly during your Neovim workflows.

When updating Neovim plugins, consider that Mason-managed LSP installations may require separate handling. The plugin management workflow applies to editing lua/plugins and lazy.lua, while Mason LSP installations have their own operational caveats during maintenance.

No, this plugin management workflow specifically applies to Neovim configurations located in the ~/.config/nvim directory. It is designed for workflows that add or remove plugins within this standard configuration path.