ESLint VS nvim-lint

An important step towards adding comprehensive support for TypeScript in a Node.js application is setting an adequate linting workflow. You can make use of the popular ESLint package to lint TypeScript code. Although it was originally written for JavaScript code, it also supports TypeScript with the help of a few plugins. Go ahead and install the eslint package in your project with the command below:

Linters are static analyses of the code meant to point to the sources of common issues. It’s nice to have a regular check that goes through your code and tells you that all is good here. eslint, a popular linter for JavaScript and TypeScript, allows for a lot of configuration. You can set the config to catch only the most problematic issues, fix the whole codebase, and integrate it with your code editor. To keep getting more value from the setup, you can continue iterating over the config—turning on or off different rules and adding framework-specific plugins. In this way, you will be able to make your code more likely to improve with time; and at the same time, every step will be small and won’t take you too much time at once.

Generally, just use a formatter and linter and do whatever those suggest. For web stuff https://prettier.io/ is a good formatter to use and eslint https://eslint.org/ a good linter. Though eslint does try to enforce style as well which conflict with prettier, but they can be configured to work together: https://www.benmvp.com/blog/prettier-eslint/

✅ Angular 13 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with [TestCafé](https://testcafe.io/ ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Analyse your project with webpack-bundle-analyzer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting ✅ AuditJS Audit this application using Sonatype OSS Index ✅ Auto-generate a CHANGELOG with auto-changelog

Fortunately, a great way to encourage your consumers to follow your best practices is through the use of ESLint, a static analysis tool to find problems in your code.

Before taking the next steps in the direction of TypeScript, we will prepare a working environment according to all industry standards. We have already set up EditorConfig so that all the files we create comply with certain rules. ESLint is a code quality control tool. It allows you to describe a list of rules for formatting code, language constructs used, and so on. This allows you to write code in a single style. If these rules are not followed, the code will be underlined in the editor. You can also run the check from the console.

Maybe ESLint has a different opinion, otherwise I see no reason not to use this. Also. if you don’t use ESLint yet, there’s undoubtedly a plug-in for your IDE 🙂

I use vale to do some prose linting. https://github.com/mfussenegger/nvim-lint has support for it

nvim-lint (minimal plugin that is a bridge from external CLI linters to the diagnostic api) has a clang-tidy integration one might be interested in https://github.com/mfussenegger/nvim-lint

You could try setting up null-ls or nvim-lint

I'm using https://github.com/mfussenegger/nvim-lint

There's also null-ls.nvim and nvim-lint but I haven't tried them myself.

Many of you are using EFM to use additional linters/diagnostics not provided by a server. There are two additional projects you should check out. nvim-lint and null-ls are basically lua/in-process wrappers of CLI linters/formatters (in the case of null-ls) that can run in-process (currently for nvim-lint, soon for null-ls) and are extremely customizable.

If you want something in lua there is nvim-lint. I have not used this but it seems like it should work with nvim-lsp but only linting from what I see.

there's https://github.com/mfussenegger/nvim-lint as an alternative to efm/diagnosticls