Change:
frameContext.window.console.error = function proxyWarn( ...args: string[] ) { <del> proxyLogger(args.map((arg: string) => utilsFormat(arg)).join(' ')); </del> <ins> if (args.every(arg => !actRE.test(arg))) { proxyLogger(args.map((arg: string) => utilsFormat(arg)).join(' ')); } </ins> return oldError(...(args as [])); }; }

Discussion:
There are some modules ( e.g: module ) within the section of the course where, when the user submits their solution ( whether correct or incorrect ), then they end up with the following warning within the console: Since this warning is not relevant to the solution submitted by the user, I think it could make the user feel confused. In order to avoid any sort of ambiguity and to keep things as clear as possible, I believe when the user submits their solution and if their submitted solution is not correct ( partially or completely ), then they should only be getting relevant error messages printed onto the console which can help them in debugging their solution, or if their submitted solution is entirely correct, then they should be getting the following messages only ( within the console ): ! Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110
I can see that the error message is pretty cryptic even though it happened somewhere along the stack trace. If you don't mind, can you comment your JSX element so that me and other people can paste the code immediately in the editor and see it for ourselves ?
Can you provide the path of this file.
If you want i can work on this issue. Can you assign this to me. I am expert in react but first timer in open source community. So apologize in advance if i am going out of way in asking this on the thread
Pretty sure that has been there forever. It looks to be caused by running tests with the production builds of React. Maybe we can just use the dev builds. Tested it briefly and it didn't seem to break anything, but I'm not sure what the reason for using the production builds is. Or maybe the error message can be silenced somehow.
Hey thanks for looking into this issue. It would be great if this error message could be silenced somehow or as you mentioned, if using dev builds solves this issue, then I think it would be a good idea to do so given that it doesn't break anything. Let me know what you think about it. Cheers!
I'm pretty sure I have seen this error on other React (maybe React/Redux) challenges as well. I'm not sure if it is just because the prod build is smaller/faster or what? I see no real harm in using the dev build and it would/should make the error go away.

But someone from the dev team will have to look at this and approve it. is using the dev build of React an option here?
I'm not entirely sure, tbh. Maybe something can provide insight on.
So, the problem is that we currently bundle react-dom-test-utils into the script that runs the tests, so changing the meta doesn't help us. However, once is in, we will have full control over the scripts that we import and can choose which build we want for the react lessons. I propose we revisit this issue once that's in main and experiment with development builds then.
I am interested to work on this issue. can anyone explain me more clearly what to do next?
Can I work on this?