ESLint

I was talking to one of our engineers on the design system team too.

And that was griping that we just have a shit ton of ESLint like rules.

And they were explaining that's how we catch stuff from seeping through if they're not using like the token packages, if they're not using components properly.

Obviously, we have a threshold.

Or is it the right token?

Yeah, that's what I mean.

Is that token being used correctly? That's hard to tell with an ESLint.

If, you know, there are certain cases where I can pick it up, but oftentimes it's just going to be too subjective for an ESLint to determine.

So if you're using Turbo repo, well, they have concepts of boundaries that you can use to encapsulate your packages.

If you use ESLint, they have plugins for applying boundaries and guardrails around your product.

So I think once you understand the concept, then you start to see the solutions that exist in many different languages.

And these guardrails specifically, these are things that are very helpful for AI these days because AI will use those tests that you have, your ESLint rules, whatever guardrails that you have to make sure that their work is complying with how you want your architecture to be structured, right?

Yeah.

Hopefully they follow the boundaries.

And so now we're on Vite Plus, right? So again, this will combine multiple tools under a single CLI, which will simplify commands.

ESLint and Prettier are now removed from that front-end setup.

The couple things to be aware of here if you're migrating to this, the lint and the formatting rules are now in the Vite config.

So with the standalone config files gone, those rules now live in that Vite config.typescript file under the lint and fmt keys.