ESLint VS nvim-lint

Have you ever used a transpiler, a linter or a code formatter, such as: Babel, ESLint or Prettier? If the answer is yes, then you've already used metaprogramming! 👏

ESLint is a JavaScript and TypeScript linting tool, which means it analyses source code and identifies possible programming problems and errors. It underlines errors in red and warnings in yellow. It is very useful to cover coding styles issues.

Best: set up an IDE (Visual Studio Code is free and an industry standard) and configure ESLint and the ESLint extension for your IDE so that you can catch errors like this before even running your script.

This is the extension for integrating the most well-known linter for JavaScript into Visual Studio Code. ESLint is a static analyzer of your source code which helps you find problems quickly. It will highlight issues in your code for all loaded files from your workspace. I don’t feel there’s much to write about here – just check their website and give this extension a try 😉

Linting is an important step in maintaining code quality, The React Library Builder uses ESLint and eslint-config-prettier for linting. You can modify linting rules by overriding them in the .eslintrc file.

Setup When I open the project in VS Code, it prompts me about ESlint and Docker apps that the project uses, so I make sure to have them. I run pnpm install command to install dependencies in the project while I'm in the project's directory folder. There are different ways to run the project in the documentation, and I want to run both frontend and backend, so I run pnpm services:start to run the project locally. If Docker is running, it should setup to host the project locally. Be sure to run pnpm services:stop when you are done, and clear the cache if you need to. If I need to use the database in some way, like testing login, I make sure to run cp ./src/db/env.example .env to get the right env file copy and then run pnpm db:init to setup the database.

ESLint to set some rules the code should abide by

We can use TypeScript compiler and ESLint for this.

Similar to how a software has integration or unit tests that are built to make sure changes in the software don’t break the entire system, we implemented tests for our documentation’s style guide using Vale and ESLint.

If you are afraid of test code leaking into the application. You can use eslint to prevent this:

This will be the third linting solution to make use of the [Neovim Diagnostic] module after null-ls and nvim-lint. All can co-exist, all have the pros and cons.

I use nvim-lint (https://github.com/mfussenegger/nvim-lint), but I still don't know exactly how to achieve your goals with it. My hunch is that it should be somewhat straightforward, since Lua code could be used to provide the executable command (i.e. if in poetry project then cmd =poetry run ...else if ... then ... end)

It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.

https://github.com/mfussenegger/nvim-lint works with the diagnostics API that was created after LSP was added, to allow non-LSP to use diagnostics API. Meaning you can see LSP and linting in the same interfaces if you use this API.

You could use null-ls as an interface between Neovim LSP client and this kind of tools. If this tools are linters, you could also use nvim-lint

I have both https://github.com/simrat39/rust-tools.nvim and https://github.com/mfussenegger/nvim-lint configured and I started noticing something that was working before had suddenly become broken, and it's not clear what changes I've made to my config (https://github.com/Integralist/dotfiles/tree/main/.config/nvim) that would have caused this error.

Other tools that can enhance neovim further are nvim-lint, null-ls and nvim-dap. Check out their documentation before doing anything, make sure you understand what they do.

Actually neovim has smth comparable to ale, it is https://github.com/mfussenegger/nvim-lint. And it leverages lsp diagnostic support in neovim, without being LSP server.

For the linting side of things I would suggest nvim-lint.