Update to 5.0.0 can no longer build about mdi-material-ui HOT 3 CLOSED

Not having an upgrade path is not a valid answer. There is no reason an icon libraries major release should blow up a dev pipeline over a dependency.

from mdi-material-ui.

It's a major release, because it breaks stuff. No need to update, there are no new icons (and I'll continue to add new icons in v4 as soon as they get released for the next few months).

See our release notes here: https://github.com/TeamWertarbyte/mdi-material-ui/releases/tag/v5.0.0
TL;DR v5.0.0 adds support for Material-UI 1.0.0, which changed the package from material-ui to @material-ui/core.

from mdi-material-ui.

@goyney 👎-ing a helpful answer is not nice. The upgrade path is to keep on v4, you will get the latest icons in future updates and everything will just work. We need v5 to keep compatible with the latest material-ui.

Also, according to semantic versioning, major versions bumps are exactly meant for this: breaking changes. It's not my fault that breaking changes tend to be breaking.

PS: I also added this to the release notes. If you don't use Material-UI 1.0.0-rc.0 (or later), just keep on v4 and enjoy all the icons. 👍

from mdi-material-ui.