Why?

Writing clean and consistent code is super important, not just for you, but for your entire team. A consistent coding style makes projects easier to maintain, reduces bugs, and helps every developer quickly understand each other’s code.

That’s exactly why we rely on ESLint, a powerful tool that analyzes your code and provides instant feedback to keep things in shape.

Problem 😬

One of the most popular ESLint style guides out there is the Airbnb ESLint Config. For years, developers have trusted it as a reliable, opinionated set of rules that enforce best practices and readable code. It became a kind of “gold standard” in the JavaScript community.

But here’s the issue:

• The Airbnb config hasn’t been updated in over 4 years.
• It doesn’t work well with ESLint 9 (and beyond).
• It lacks TypeScript support.
• It contains some rules that create unnecessary friction.

In today’s fast-moving JavaScript ecosystem, three years is a long time. By the time ESLint 9 came around, the old Airbnb config simply couldn’t keep up.