Tara Dia

Is this any closer to being fixed or is there something I can do to suppress the warning on my end? Besides the excellent suggestion to edit webpack.config.js. I would...

``` global.structuredClone = val => { return JSON.parse(JSON.stringify(val)) } ``` is what worked for me. But is this going to be fixed?

@rodpatulski Thank you for your response! I put ```import '@testing-library/react/dont-cleanup-after-each';``` in the file that is breaking and unfortunately it is still breaking and in the same way. Which is weird...

@rodpatulski 18.2.0

Do you mean in order to troubleshoot it? Because I can't permanently switch to react 17, my devops team is adamant we stay on 18.

Thank you! That does make it possible to test my other parts of the component without breaking but I was hoping there would be some way around mocking the library...

@sohail-coder Not really. I'm mocking out the module at the moment but I'd prefer to be able to test without mocking

@rodpatulski Unfortunately I am getting the same bug

This is still happening

Even just a list of the props that are available would be awesome