How to avoid build failure from eslint violations

[ackmanx]

I created a fresh project using CRA, and then added a custom eslint config with a single rule, no-console and set it to error log level.

When running yarn start to do development, and putting in a console log, the whole build fails and I get a generic error page saying the build failed because there was a console log. But, I put the log there to debug the app, and this isn't a production build.

I also tried seeing if this could be related to custom eslint configs so I violated the rule-of-hooks rule that is default with CRA and saw the same thing happen.

How can I develop with a linting error present?

[gone-skiing]

Bump, we are also facing this issue... How do we get some info on this?

[sean256]

I'm having the same issue. I need to be able to dev with "eslint errors" without being blocked.

[ackmanx]

I cross-posted on SO too (https://stackoverflow.com/questions/64654934/how-to-avoid-build-failure-from-eslint-violations-with-react-scripts-create-reac), but no activity there as well.

For now, I've set rules to warn so they don't fail local development but will fail on the CI

[gone-skiing]

I created repo that reproduces the issue: #10062