A debug adapter for Neovim that enables debugging of Lua plugins and configuration files using the Debug Adapter Protocol.
one-small-step-for-vimkind is a debug adapter for Neovim that allows developers to debug Lua code running within Neovim instances using the Debug Adapter Protocol. It solves the problem of inspecting and troubleshooting Lua plugins, configurations, and scripts directly in the editor environment. By providing breakpoints, stepping, and variable inspection, it enhances the development workflow for Neovim plugin authors.
Neovim plugin developers and users who write Lua configurations and need to debug their code. It is particularly useful for those building or maintaining complex Lua-based Neovim plugins.
Developers choose osv because it integrates seamlessly with Neovim via the DAP protocol, offering a standardized debugging experience. Unlike limited alternatives, it provides full debugging features like breakpoints, stepping, and variable inspection specifically tailored for the Neovim Lua environment.
Debug adapter for Neovim plugins
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Tailored for Lua in Neovim, enabling direct debugging of plugins and configuration files like init.lua within the editor, as highlighted in the key features.
Implements the Debug Adapter Protocol, ensuring compatibility with clients like nvim-dap and providing a standardized debugging interface, per the philosophy section.
Supports breakpoints, stepping, variable inspection, and real-time modification, with most handlers implemented as shown in the status list.
Captures debuggee output including Neovim messages using :redir, allowing developers to monitor logs during sessions, though with noted side-effects.
Missing key handlers like terminate and setFunctionBreakpoints, limiting advanced debugging capabilities compared to full DAP support, as acknowledged in the status.
Requires configuration with nvim-dap, custom keybindings, and has known issues with plugins like flatten.nvim and fzf-lua, adding to setup overhead and potential instability.
Breakpoints are path-sensitive and can fail with symlinks (e.g., from packer.nvim) or cloud services like Dropbox, leading to unreliable debugging, as detailed in troubleshooting.