You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The material-table package has a dependency on @material-ui/pickers 3.2.2 which does not support React v17 and this npm package is also being deprecated anyway. See this link -> mui/material-ui-pickers#2157.
The latest version of pickers is 3.3.10 so at a minimum we need this updated to that. Beyond that this package needs to be updated to use React v17 compatible dependencies.
Here's the error I get when building my application (which I tracked to this package's dependency):
npm WARN @material-ui/[email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself. npm WARN @material-ui/[email protected] requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
The text was updated successfully, but these errors were encountered:
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.
The material-table package has a dependency on @material-ui/pickers 3.2.2 which does not support React v17 and this npm package is also being deprecated anyway. See this link -> mui/material-ui-pickers#2157.
The latest version of pickers is 3.3.10 so at a minimum we need this updated to that. Beyond that this package needs to be updated to use React v17 compatible dependencies.
Here's the error I get when building my application (which I tracked to this package's dependency):
npm WARN @material-ui/[email protected] requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself. npm WARN @material-ui/[email protected] requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
The text was updated successfully, but these errors were encountered: