-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Material table not install with react 17.0.2 #2874
Comments
So you cannot use it? Well, you maybe don't know this yet, but you've actually had some luck man. |
why? lol this soo bad? |
I would have thought this would fix it? |
Commented on what I think is causing it, TLDR; I think |
Any updates on this? Need to use material table with a React 17 project. Can someone fix the peer dependency on @material-ui/pickers@"3.2.2" |
|
Having the same issue, not installable on 17.0.2, caused by dependency on @material-ui/pickers@"3.2.2". |
same |
+1 for this, already using in a React 17 project, cannot correctly npm update, in case of force install or force audit fix, material-table messes up own versions crashing the whole applicatoin, unbelievable... I advertise this plugin to my colleagues as one of the bests with no issue at all, and then, out of the blue a major blocker issue for months now... don't even use picker in mattable, Please fix this ASAP |
@IcarusHU I just used this maintained fork instead: https://material-table-core.com/ |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You can reopen it if it required. |
did anyone got the solution for this issue or we belive someday God will fix this. |
using --force Recommended protections disabled.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/react
npm WARN react@"^17.0.0" from the root project
npm WARN 3 more (material-table, @material-ui/core, react-dom)
The text was updated successfully, but these errors were encountered: