Find and fix problems in your JavaScript code. (by eslint)

ESLint Alternatives

Similar projects and alternatives to ESLint

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better ESLint alternative or higher similarity.

ESLint reviews and mentions

Posts with mentions or reviews of ESLint. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-25.
  • Complete rewrite of ESLint (GitHub discussion by the creator)
    5 projects | | 25 Nov 2022
  • Nodejs Boilerplate with Typescript and Express
    4 projects | | 24 Nov 2022
  • Front-end Guide
    54 projects | | 23 Nov 2022
    A linter is a tool to statically analyze code and finds problems with them, potentially preventing bugs/runtime errors and at the same time, enforcing a coding style. Time is saved during pull request reviews when reviewers do not have to leave nitpicky comments on coding style. ESLint is a tool for linting JavaScript code that is highly extensible and customizable. Teams can write their own lint rules to enforce their custom styles. At Grab, we use Airbnb's eslint-config-airbnb preset, that has already been configured with the common good coding style in the Airbnb JavaScript style guide.
  • How to add ESLint, Prettier, and Husky to your Web / NodeJS project
    2 projects | | 20 Nov 2022
    Every web developer that writes in NodeJS/React/NextJS/Angular/Vite should use ESLint, Prettier, and Husky. You must be familiar already with ESLint and maybe you have heard about the other two before but if not, I'm going to do some order in your head about each one and how you can use it and implement it in your own project. So let's get started.
  • DPS909 Blog :Release 0.3 External Project Contribution
    2 projects | | 17 Nov 2022
    So I have decided to include the linter into their project. I have created the new issue Suggesting them to add the ​ESLint into their current project.It will help them to avoid certain code patterns that often lead to bugs. And I have Create a simple "one-step" solution for running your linter on the entire project from the command line. Furhtermore, I have added Pre-commit and Pre-push This is a pretty important step. This will ensure that before any developer commits any code, the changes made by him are validated with ESLint, and the code is properly formatted.
  • Javascript Developer Roadmap: Zero to Hero
    4 projects | | 17 Nov 2022
    Set up ESlint in your projects to follow linting rules and fix errors during development. Use this extension.
  • Release 0.3 - Working with external repository
    2 projects | | 16 Nov 2022
    Adding Prettier is a bit difficult. Trying to figure out the format of how the author wrote his code has to be put into considerion, because changing everything drastically will cause a setback for when the author and those whom had worked for it touched the code. Once I finish adding the prettier I decided to add the ESLint, unlike the former that simply changes the style, this would basically remove any inconsistencies and repetition, and tell the user about any codes that does not follow a specific standard. This is important, because it can directly impact the amount of bugs that will occur in the future. Once I have added it, I had to individually check the files that it highlights and change their values to ensure that no possible bugs can occur in the future. Once this is done, I added a pre-commit hook to ensure that any commit that the user does gets checked before passing.
  • Conditional Logging to the JavaScript Console
    4 projects | | 14 Nov 2022
    The JavaScript console is a very useful debugging tool, but it can also introduce a very simple security risk into your application: console method calls that aren't removed before code is deployed can leak sensitive information to the browser. That's why many developers use a linter to warn about console method calls and other issues. (On RedBit's web team, we use husky to run the linter on a pre-commit hook so that console method calls are never committed by accident. We've found that many small bugs can be avoided by making linting mandatory before committing code.)
  • Commit Like a PRO
    3 projects | | 11 Nov 2022
    ESLint Docs
  • Advice for experienced dev taking on front-end role?
    6 projects | | 11 Nov 2022
    Tooling takes away alot of headaches and saves yourself from "being clever" (stupid). Most front-end tooling can be run out of the nodeJS runtime, so even if your stack isn't JS oriented, it's still worth running node. The obvious shoutouts: Vite, eslint, stylelint, postCSS, browserslist. Playwright is somethin else you can give a look at if your scope of work is large enough.
  • A note from our sponsor - Scout APM | 27 Nov 2022
    Scout APM is great for developers who want to find and fix performance issues in their applications. With Scout, we'll take care of the bugs so you can focus on building great things 🚀. Learn more →


Basic ESLint repo stats
4 days ago
Truly a developer’s best friend
Scout APM is great for developers who want to find and fix performance issues in their applications. With Scout, we'll take care of the bugs so you can focus on building great things 🚀.