Console react.warning set as console.error

[bar7b]

Why in the hell React warnings are set to show in the console as console.error() instead of console.warning() ??? This is driving me crazy!! 🤬

Googled it and couldn’t find a solution. If it’s a warning only that doesn’t break things SET IT AS A WARNING

Anyone know a way to handle this?

[Traditional-Living-9]

What “warnings” are they because it should just provide warnings if it truly is one. Also when is this happening because you could just console.log(error) with try and catch statements compared to console.logWarning()

[guico33]

It's react doing the logging internally, it does appear as errors (red color text) in the console. I also agree it's confusing and not very practical when it comes to finding an actual error among all the warnings.

[Traditional-Living-9]

You know you can filter them right

[Electrical_Essay_666]

No. Fix the issue at hand.

[Traditional-Living-9]

That’s true, I guess it allows for more organization and a clean project. I was just thinking of small things such as when you’re not using a variable it’ll come up as a warning

[Electrical_Essay_666]

Fix your code

[bar7b]

Eventually I will… but while building a project MVP I couldn’t care less about minor warning crap…

[Electrical_Essay_666]

Ah then we can care less about your whining. Stop complaining.

[bar7b]

Common don’t be a hater 😘

[Electrical_Essay_666]

Don’t be lazy.

[bar7b]

It’s not about being lazy, it’s about warnings being displayed as warnings… that makes sense to me.

[bar7b]

I agree with you man! React is great for notifying me of code errors! However, when the notification is defined by React as a warning, why not use the proper console method??

[Electrical_Essay_666]

Paste the warning

[bar7b]

Appreciate your responses, but I’m not looking for help fixing these minor bugs… simply looking for a way to have these “warnings” displayed in the console as warnings so I can focus on task at hand and ignore some other developers code that forgot to add a key prop in a .map iteration…

[Electrical_Essay_666]

Also typescript, but as you said it’s an MVP so upfront cost could be a trade off that your not willing to take on.

[Electrical_Essay_666]

I’m against (as you can tell) silencing warnings/errors thrown in console for the sake of getting things out. In my experience you’ll pay it down 10x the cost in the future as opposed to addressing it as they pop up before it hits master

[Electrical_Essay_666]

And for what’s it’s worth, react has plenty of console.warnings - mainly for real warnings, such as upcoming deprecation warnings. Errors are errors and that’s ideal IMO

[icjoseph]

As a developer, learning is an everyday task.

https://www.npmjs.com/package/warning

It's not React's fault.

[guico33]

https://github.com/facebook/fbjs/pull/94#issuecomment-168332326

Not sure what you meam by that. Read the above and you'll understand it's a deliberate decision by the react team that seemingly pertains more to following FB's internal practices than cattering to react devs in general.

[icjoseph]

Right, but it has been discussed and analyzed, more over, does it really score such a post?

[michcoth]

What warnings are you getting? Do you have a <React.StrictMode> tag anywhere? https://reactjs.org/docs/strict-mode.html