An asynchronous linter plugin for Neovim that complements the built-in Language Server Protocol support.
nvim-lint is an asynchronous linter plugin for Neovim that runs external linters and displays their results as diagnostics within the editor. It complements Neovim's built-in Language Server Protocol support by providing linting for languages without LSP servers or where standalone linters are more effective. The plugin integrates directly with Neovim's diagnostic system, offering a lightweight and focused alternative to broader linting solutions.
Neovim users (version 0.9.5+) who need asynchronous linting for various programming languages, especially those working with languages lacking robust LSP support or preferring standalone linters.
Developers choose nvim-lint for its simplicity, performance, and tight integration with Neovim's native diagnostics. Unlike more comprehensive tools, it avoids duplicating LSP functionality, resulting in a faster, more focused linting experience that works seamlessly alongside Neovim's built-in features.
An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Runs linters in the background without blocking the editor, ensuring a smooth editing experience as highlighted in the key features.
Includes built-in support for over 150 linters across programming languages and filetypes, as listed in the README's comprehensive table.
Reports diagnostics via vim.diagnostic, enabling seamless use with Neovim's diagnostic display and configuration, per the plugin's philosophy.
Allows defining custom linters with parsers for Lua patterns, errorformat, and SARIF output, detailed in the Custom Linters section.
The README explicitly warns that linters may execute local executables (e.g., ./node_modules/.bin/eslint), making it unsafe for untrusted repositories without careful oversight.
Requires users to set up autocmds and configure linters per filetype manually, which can be complex compared to more automated or opinionated tools.
Focuses solely on running external linters and parsing output, lacking built-in code fixes, intelligent refactoring, or deep integration beyond diagnostics.