TypeError: Cannot read properties of null (reading 'usestate') at useProviderColorScheme

[limpid crater]

I can't find a solution on how to fix this warning, I already double and triple checked our React versions, mantine versions and how I implement hooks in the application. I found an old thread in the support archive saying it could have been the create-react app fault, which I'm not using in this project

I'm using Mantine 7.7.0 and Next 13.4.19

[waxen grail]

Did you add use client?

[limpid crater]

the useState that trows an error is being used inside useProviderColorScheme, and yes it has use client

[zealous marsh]

You have multiple versions of react loaded into your bundle

[limpid crater]

Do you mean multiple *different * versions? Because I have multiple import of React inside the bundle, but all with the same version

[zealous marsh]

Does not matter what version they are. You should aleays have only one react in your bundle.

[limpid crater]

So in the situation where I have mutiple package.json (a ui library and a main application for example), I need to make sure to import react in only one otherwise it will show this warning. So if I go in a monorepo approach I will always encounter this

[zealous marsh]

No, it is not related to monorepo. Mantine codebase is a monorepo, it includes ~20 packages and 2 apps, there are no issues, everything uses the same react version

[limpid crater]

Ok, so theoretically speaking if I centralized how I define the react dependency across the bundle and make sure that each packages/application uses that shared react dependency, the warning should disappear

[limpid crater]

I moved every "react": "18.2.0", "react-dom": "18.2.0" from the single packages to the root package and still the error is there, now I should only have just this version of react, but it doesn't seem to fix the issue

[halcyon shell]

The UI package should define React as a dev or peer dep.

Also, make sure to completely remove your node_modules, and maybe even your lock file once and reinstall. Sometimes versions get sort of "stuck"