Don't remove them at random. Remove them where data enters your app, because that's where the runtime errors come from.
- Make them visible but not blocking:
// eslint "@typescript-eslint/no-explicit-any": "warn" - Start with API responses and form data. Give them a real type, ideally parsed:
Your
const Order = z.object({ id: z.string(), items: z.array(Item) }); const order = Order.parse(await res.json()); // throws early with a clear message.map of undefinederrors will surface as a parse error at the boundary instead of deep in a component. - Where you really don't know the type yet, use
unknown, notany. TypeScript forces you to check before use. - Fix everything downstream as the errors appear, one file per commit.
212 sounds like a lot, but most come from a handful of untyped functions. Fixing those 10 usually makes half the rest pointless.