NPM (WARN) ERESOLVE overriding peer dependency while resolving [email protected]

[kblovett]

Brand new empty create-react-app. Just installing all the libraries I'll need. MUI 5 already installed, and npm is returning error feedback upon installing mui-datatables

Expected Behavior

I expect to be able to install mui-datatables without any warnings or errors, as long as listed dependencies are met.

Current Behavior

npm i mui-datatables

npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: [email protected] npm WARN node_modules/react npm WARN peer react@">=16.8.0" from @emotion/[email protected] npm WARN node_modules/@emotion/react npm WARN peer @emotion/react@"^11.0.0-rc.0" from @emotion/[email protected] npm WARN node_modules/@emotion/styled npm WARN 6 more (@mui/material, @mui/styled-engine, @mui/system, ...) npm WARN 21 more (@emotion/styled, @mui/base, @mui/icons-material, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer react@"^15.3.0 || ^16.0.0-alpha" from [email protected] npm WARN node_modules/react-virtualized npm WARN react-virtualized@"^9.21.2" from [email protected] npm WARN node_modules/react-sortable-tree-patch-react-17 npm WARN npm WARN Conflicting peer dependency: [email protected] npm WARN node_modules/react npm WARN peer react@"^15.3.0 || ^16.0.0-alpha" from [email protected] npm WARN node_modules/react-virtualized npm WARN react-virtualized@"^9.21.2" from [email protected] npm WARN node_modules/react-sortable-tree-patch-react-17 npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: [email protected] npm WARN node_modules/react-dom npm WARN peer react-dom@"^17.0.0" from @mui/[email protected]
npm WARN node_modules/@mui/base npm WARN @mui/base@"5.0.0-alpha.69" from @mui/[email protected]
npm WARN node_modules/@mui/material npm WARN 10 more (@mui/material, @testing-library/react, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer react-dom@"^15.3.0 || ^16.0.0-alpha" from [email protected] npm WARN node_modules/react-virtualized npm WARN react-virtualized@"^9.21.2" from [email protected] npm WARN node_modules/react-sortable-tree-patch-react-17 npm WARN npm WARN Conflicting peer dependency: [email protected] npm WARN node_modules/react-dom npm WARN peer react-dom@"^15.3.0 || ^16.0.0-alpha" from [email protected] npm WARN node_modules/react-virtualized npm WARN react-virtualized@"^9.21.2" from [email protected] npm WARN node_modules/react-sortable-tree-patch-react-17

added 20 packages, and audited 1491 packages in 3s

Steps to Reproduce (for bugs)

1. run create-react-app
2. npm i @mui/material
3. npm i @mui/icons-material
4. npm i tss-react (got same error both with and without this package)
5. npm i mui-datatables

Your Environment

"dependencies": { "@emotion/react": "^11.8.1", "@emotion/styled": "^11.8.1", "@fontsource/roboto": "^4.5.3", "@mui/icons-material": "^5.4.2", "@mui/material": "^5.4.2", "@redux-devtools/extension": "^3.2.2", "@sendgrid/mail": "^7.6.1", "@testing-library/jest-dom": "^5.16.2", "@testing-library/react": "^12.1.3", "@testing-library/user-event": "^13.5.0", "axios": "^0.26.0", "bson-objectid": "^2.0.2", "date-fns": "^2.28.0", "jsonwebtoken": "^8.5.1", "lodash": "^4.17.21", "mui-datatables": "^4.1.2", "react": "^17.0.2", "react-dom": "^17.0.2", "react-keyed-file-browser": "^1.14.0", "react-redux": "^7.2.6", "react-router-dom": "^6.2.1", "react-toastify": "^8.2.0", "react-youtube": "^7.14.0", "redux": "^4.1.2", "redux-thunk": "^2.4.1", "tss-react": "^3.4.1", "web-vitals": "^2.1.4" }, "devDependencies": { "react-scripts": "5.0.0" },

Tech	Version
Material-UI	5.4.2
MUI-datatables	4.1.2
React	17.0.2

[binarykitchen]

This warning is annoying. Can anyone look at this please? Thanks

[kostyakazmiruk]

++

[ensemblebd]

https://github.com/frontend-collective/react-sortable-tree/issues/916

react-sortable-tree must resolve it's reference and update then mui-datables can++

considering they have 43 pending pull requests over there, and 25 here, I think it's safe to say it may be a while to resolve this. Sometimes, we just gotta fork this stuff, tweak it, publish to private repo, swap deps with a scope, and call it a day. =/