Avoid App to Crash after Eslint Error

[MRSTIGLITZ]

How can I avoid my react app to crash after a eslint error?
I just create an app using npx create-react-app and it comes with react-scripts: 4.0.0, but think something change, because before was using in another app version 3.4.1 and my app wasn't crashing, just seeing the errors on my editor.

[ChristianMurphy]

CRA 4 added new ESLint rules:

We've upgraded to ESLint 7 and added many new rules including some for Jest and React Testing Library as well as the import/no-anonymous-default-export rule. We've also upgraded eslint-plugin-hooks to version 4.

https://github.com/facebook/create-react-app/releases/tag/v4.0.0

Disabling ESLint for a folder or overall is an option (see #10021), but may not be a good idea, as the ESLint rules CRA provides by default highlight potential errors.
Updating the source code to resolve the errors, rather than hiding them with ignores/config, it likely the best solution.

[stealthman22]

Please it's too opinionated, some of these errors aren't errors, it's just me testing a component.
Now I get more errors because I can't test a component without CRA crashing.
If the prototypes aren't resolved it crashes, if I call in something I haven't used it crashes e.t.c
This means sometimes I have to develop in the blind, and test after all things are resolved.
Not the best dev experience. It should warn me, but not hinder me.
Thank You