material-ui-icons-next wrong peerDependencies

Currently I’m using material-ui v0.20 and I want start the migration to v1. As it is written on the page: https://material-ui-next.com/guides/migration-v0.x I’ve installed the package material-ui-next to have to versions of material-ui (npm install material-ui-next).

Now I want to use material-ui-icons package. So my idea was to install the material-ui-icons-next that analogous should have the dependencies to material-ui-next not to material-ui package.

Current Behavior

npm WARN material-ui-icons-next@1.0.0-beta.17-next requires a peer of material-ui@^1.0.0-beta.16 but none was installed.

material-ui-icons-next package.json:

"peerDependencies": {
    "material-ui": "^1.0.0-beta.16",
    "react": "^15.3.0 || ^16.0.0",
    "react-dom": "^15.3.0 || ^16.0.0"
  }

Expected Behavior

material-ui-icons-next package.json:

"peerDependencies": {
    "material-ui-next": ...
}

[oliviertassinari]

Current workaround: https://github.com/mui-org/material-ui/pull/8473#issuecomment-333472103

This issue will be solved once we release Material-UI under a new npm organization in #9673. We will be able to close #9469 too.

[oliviertassinari]

peerDependencies: material-ui@^1… OR material-ui-next@^1…

This would suppress the warning. But I’m not convinced it’s a good thing. Especially given the situation is already pretty ugly with:

import SvgIcon from 'material-ui-next/SvgIcon';
global.__MUI_SvgIcon__ = SvgIcon;