rslint VS ESLint

Author here. A few other Rust projects to note that I didn't mention in the original post I've since found:

- Boa (JS engine in Rust) – https://github.com/boa-dev/boa

- RSLint (JS/TS linter in Rust) – https://github.com/rslint/rslint

- Node version manager in Rust – https://github.com/Schniz/fnm

If you know of any other popular ones, let me know. I'm keeping a list :)

[4]: https://github.com/rslint/rslint

ESLint for code linting

prettier and eslint are used to format our JSON, YAML, and markdown files.

Please, don’t waste your and others' time on manually checking indents or formatting rules. And write them down instead of saying “We always do it that way” during code review. I know that “spaces vs tabs” is a holy war in programming but you have to decide that battle for your team. Add tools like eslint or prettier and a set of rules to your repository. Automate that checks. Test your formatting on pre-commit or creating merge requests. Define rules in a transparent way — not only in your head. And let a computer do that simple checks — it is the best at that!

Leverage eslint to find those white-space characters at the beginning and the end of string values. First do a

We'll use ESLint with some plugins, alongside Prettier for project linting & file formatting.

Syntax errors are notorious in dynamic languages since there is no compiler. Thus you write code, have no idea if it’s right, and just run it to see if it is. The pro’s here is dynamic languages tend to be fast so this process of “does it work? does it work? does it work?” can be done many times a minute. As code bases grow, however, this starts to get tedious and error prone. Many languages have linting tools to help with this like ESLint for JavaScript and Black for Python which adds tooling complexity, but with the pro meaning you may keep the same speed of iteration.

ESLint is a tool that will analyze your JavaScript code and let you know if problems exist within it while you're coding. If you want to avoid running into common syntax errors or other simple errors before you run your code in a JavaScript Runtime Environment like a browser, then you should start using ESLint today. You can use ESLint to make your coding life easier and I'll show you how. To find out more about ESLint, check out their documentation here. In short, after setting up ESLint in VSCode, you'll be able to find problems in your code and fix them before ever running it in the browser. Check out my blog post about how to set up ESLint in VSCode.

In this article we'll take a look at how tools like ESLint and Prettier can help us never have to think about class names again, and provide some helpful guidance along the way.

ESLint, prettier - For linting and code formatting

First off, use a linter like eslint. It will help you clean up your code and find mistakes.