none-ls.nvim

<!-- markdownlint-configure-file
{
  "line-length": false,
  "no-inline-html": false
}
-->

# none-ls.nvim

`null-ls.nvim` Reloaded, maintained by the community.

Only the repo name is changed for compatibility concerns. All the API and future
changes will keep in place as-is.

## Migration

Replace `jose-elias-alvarez/null-ls.nvim` with `nvimtools/none-ls.nvim` in your
choice of package manager.

That's it.

## Community

Open a pull request to become a collaborator. If you have contributed to
`null-ls.nvim` before, simply open an issue or comment on that commit.

If you want to make changes, open a new pull request. Find another collaborator
to review your changes, as a review is required for the PR to be merged by
yourself (subject to change if there are more collaborators in the future).

---

# null-ls.nvim

Use Neovim as a language server to inject LSP diagnostics, code actions, and
more via Lua.

## Motivation

Neovim's LSP ecosystem is growing, and plugins like
[telescope.nvim](https://github.com/nvim-telescope/telescope.nvim) and
[trouble.nvim](https://github.com/folke/trouble.nvim) make it a joy to work with
LSP features like code actions and diagnostics.

Unlike the VS Code and coc.nvim ecosystems, Neovim doesn't provide a way for
non-LSP sources to hook into its LSP client. null-ls is an attempt to bridge
that gap and simplify the process of creating, sharing, and setting up LSP
sources using pure Lua.

null-ls is also an attempt to reduce the boilerplate required to set up
general-purpose language servers and improve performance by removing the need
for external processes.

## Status

null-ls is in **beta status**. Please see below for steps to follow if something
doesn't work the way you expect (or doesn't work at all).

null-ls is developed on and tested against the latest stable version of Neovim.
Support for versions built from `HEAD` is provided on a best-effort basis, and
users are encouraged to contribute fixes to any issues exclusive to these
versions.

## Features

null-ls sources are able to hook into the following LSP features:

- Code actions

- Diagnostics (file- and project-level)

- Formatting (including range formatting)

- Hover

- Completion

null-ls includes built-in sources for each of these features to provide
out-of-the-box functionality. See [BUILTINS](doc/BUILTINS.md) for a list of
available built-in sources and [BUILTIN_CONFIG](doc/BUILTIN_CONFIG.md) for
instructions on how to set up and configure these sources.

null-ls also provides helpers to streamline the process of spawning and
transforming the output of command-line processes into an LSP-friendly format.
If you want to create your own source, either for personal use or for a plugin,
see [HELPERS](doc/HELPERS.md) for details.

## Setup

Install null-ls using your favorite package manager. The plugin depends on
[plenary.nvim](https://github.com/nvim-lua/plenary.nvim), which you are
(probably) already using.

To get started, you must set up null-ls and re