Adding Linter To Legacy Codebase

So you thought adding ESLint to that 5-year-old codebase would be a good idea? Congratulations, your entire screen is now a sea of red squiggly lines. Every file. Every function. Every variable named "data" or "temp" from 2018.

The linter is basically Oprah now: "You get a warning! You get a warning! EVERYBODY GETS A WARNING!" Turns out the previous dev team had some... creative interpretations of code standards. Who needs semicolons anyway? Const? Never heard of her. Unused variables? They're just there for moral support.

Now you have two choices: spend the next three months fixing 47,000 linting errors, or add that sweet // eslint-disable at the top and pretend this never happened. We both know which one you're picking.