Jose Alvarez

@CroPhYPtic This looks good - the only changes I would make before putting in a PR would be to [use the style of existing built-in sources](https://github.com/jose-elias-alvarez/null-ls.nvim/tree/main/lua/null-ls/builtins/diagnostics) (which is slightly different...

No idea on this one, and I don't have a Windows PC to investigate. It may be related to #1341.

Unfortunately the log makes it pretty clear that this is an issue with `dprint`. Unless they add some way to support `stdin` without specifically passing in a filepath (which seems...

> There are two problems: (i) DID_OPEN called too many times, and (ii) it's also strange that the linters were marked as `method = ON_SAVE` so should have not been...

You're probably aware of this, but you can just run `null_ls.disable({ name = "vale" })` after registering the source. This seems like a pretty niche use case, but if you...

> I can open a new issue, but it would also be nice to be able to do it on a per-buffer basis, the immediate case I can think of...

> Yeah, for example if you accidentally select a large compiled `.js` file in a telescope, you end up with eslint instances pegged at 100% cpu that don't properly shut...

If an interested user can figure out how to automate this, I'd be happy to include it. See #949 for a possible approach.

Closed by #1558

Note that there is a [Rome language server](https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rome) available via nvim-lspconfig. Unless there's a good reason to use the CLI over the language server, that should provide a better experience.