react: Stop showing warnings as errors.

@Elijen you’re expected to prevent the warnings by fixing your code. If they’re not actionable then that’s a problem with those specific warnings, not warnings in general.

maybe this code snippet would help some of you. I’m using this myself:

const errorsToWarn: string[] = [
    "Warning:",
];
const oldConsError = console.error;
console.error = function(...args: any) {
    let toWarn: boolean = false;

    if (typeof args[0] === 'string') {
        errorsToWarn.map(function(_s: string) {
            if (args[0].startsWith(_s)) {
                toWarn = true;
            }
        })
    }

    toWarn ? console.warn(...args) : oldConsError(...args);
}

I do agree with @Elijen. A warning should be logged via console.warn() rather than console.error(). That would make filtering in dev tools more convenient.

@gaearon This is just an example. I know this error should be fixed by React Bootstrap, but what concerns me is the React behavior where warnings are printed as errors which makes debugging and development hard (can’t filter these out from JS console).

That’s why I think usage of console.warning should be considered.

I can’t believe it’s 5 years later and this has never been fixed! Why not? Am I missing something?

Agree with this as well. We should all fix and prevent warnings of course, however the argument is a warning is not an error and shouldn’t displayed as such.

I agree with @DieserMerlin. These are often errors which I cannot fix or that are unrelated to my assigned tasks in a project. It becomes hard to spot when a real error occurs.

Showing warnings as errors is very unconventional and should at least be configurable.

This is so annoying, why is this still the case? Just print warnings as warnings and errors as errors… 😅

This is especially uncomfortable if the warnings come from a library you depend on (in my case material-ui). In this case you can’t do anything about the actual warning but always think there’s an error in your code as react shows the warnings as errors.

“our warnings are just as important as your errors” - React

Yeah I don’t get it. My QA team isn’t so concerned with whether or not we have a key on an element (although you may argue they should, that’s another conversation), and digging through to find an actual error is time consuming.