News for hackers. Stuff that matters.

A comment on PSA: React 18 calls code twice in strict dev mode to detect side effects. Parent comment

Re:PSA: React 18 calls code twice in strict dev mode to dete... by lioeters on Sunday April 10, 2022 @01:26PM (#30979355)
Monkey-patching console.log sounds so hacky..

> In React 17, React automatically modifies the console methods like console.log() to silence the logs in the second call to lifecycle functions. However, it may cause undesired behavior in certain cases where a workaround can be used.

> Starting from React 18, React does not suppress any logs. However, if you have React DevTools installed, the logs from the second call will appear slightly dimmed. React DevTools also offers a setting (off by default) to suppress them completely.

[ Parent | on HN ]
Re:PSA: React 18 calls code twice in strict dev mode to dete... by marcus_cemes on Sunday April 10, 2022 @04:33PM (#30981420)
Also, these types of global modifications make such libraries fundamentally incompatible with projects such as Tauri that focuse on safety and security. In a recent video of theirs they mentioned that of the popular frameworks, the only one that didn't seem to do any dodgy modifications of the global scope was Svelte (they didn't mention which frameworks failed the test, but I imagine React was one of them).
[ Parent | on HN ]
Re:PSA: React 18 calls code twice in strict dev mode to dete... by joshribakoff on Sunday April 10, 2022 @05:20PM (#30981828)
It’s totally opt in, and in development only, so react doesn’t prevent you from using that other lib
[ Parent | on HN ]
Re:PSA: React 18 calls code twice in strict dev mode to dete... by SirHound on Sunday April 10, 2022 @03:29PM (#30980803)
It is, I have lost tens of hours to this over the last couple years.
[ Parent | on HN ]