How can I avoid DEV build failures due to eslint?

[sean256]

Searching around lead me to a bunch of unanswered "Discussions", such as: #9959

So I hope this issue will get us an answer faster.

Summary: I am extending eslint with a lot of non-logic-breaking errors, like code style, no console, etc. When developing locally using yarn start I don't want to make sure all of my code fits our style guid while I'm working.

[ahmed2m]

Probably related to this #9929

[rswerve]

Probably related to this #9929

I think that's slightly different. The user doesn't want to disable ESLint, they want to return to the pre-4.0 behavior of the linter showing errors in the console without blocking compilation. This one is the same issue as #9887 and #10021 and #9959

[gaearon]

Duplicate of #9887, let's consolidate there.