4 Commits

Author	SHA1	Message	Date
Luna Ruan	60a30cf32e	Console Logging for StrictMode Double Rendering (#22030) ... React currently suppress console logs in StrictMode during double rendering. However, this causes a lot of confusion. This PR moves the console suppression logic from React into React Devtools. Now by default, we no longer suppress console logs. Instead, we gray out the logs in console during double render. We also add a setting in React Devtools to allow developers to hide console logs during double render if they choose.	2021-08-25 15:35:38 -07:00
Sebastian Markbåge	940f48b999	Avoid passing custom stacks to console.error (#18685) ... * Detect double stacks in the new format in tests * Remove unnecessary uses of getStackByFiberInDevAndProd These all execute in the right execution context already. * Set the debug fiber around the cases that don't have an execution context * Remove stack detection in our console log overrides We never pass custom stacks as part of the args anymore. * Bonus: Don't append getStackAddendum to invariants We print component stacks for every error anyway so this is just duplicate information.	2020-04-21 09:22:46 -07:00
Dan Abramov	3c54df0914	Fix missing stacks in WWW warnings (#17638)	2019-12-17 15:21:18 +00:00
Dan Abramov	0cf22a56a1	Use console directly instead of warning() modules (#17599) ... * Replace all warning/lowPriWarning with console calls * Replace console.warn/error with a custom wrapper at build time * Fail the build for console.error/warn() where we can't read the stack	2019-12-14 18:09:25 +00:00