mui-component-mapper v4.1.0 not works with react19

[RomanKosovnenko]

Scope: mui-component-mapper

Description
When upgrading to react 19 with mui component mapper, there is an error:

npm error   react@"^19" from the root project
npm error   peer react@"^17.0.2 || ^18.0.0 || ^19.0.0" from @data-driven-forms/[email protected]
npm error   node_modules/@data-driven-forms/mui-component-mapper
npm error     @data-driven-forms/mui-component-mapper@"^4.1.0" from the root project
npm error   7 more (@data-driven-forms/react-form-renderer, react-dom, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^17.0.0 || ^18.0.0" from @mui/[email protected]
npm error node_modules/@mui/x-date-pickers
npm error   @mui/x-date-pickers@"^6.20.2" from the root project
npm error   peer @mui/x-date-pickers@"^5.0.1 || ^6.13.0" from @data-driven-forms/[email protected]
npm error   node_modules/@data-driven-forms/mui-component-mapper
npm error     @data-driven-forms/mui-component-mapper@"^4.1.0" from the root project

Please, consider upgrading to at least v7

Schema

not relevant

[Hyperkid123]

RIght, we need to bump the MUI packages as well.

[RomanKosovnenko]

Sorry to bother you, but this is quite critical for us. Do you have an approximate timeline for when it might be completed?

[Hyperkid123]

I'll try to get at it today. I have other responsibilities though

[Hyperkid123]

We are currently blocked on this: final-form/react-final-form#1046

There was an effort to run on a custom form state manager. Though working, I do not have the capacity right now to ensure we have a stable release. If that PR does not get merged soon, I'll make a fork to increase the version range (the code works just fine). I'll see if I can find some colleagues to start contributing to the project.