Impossible to use with angular 5.2.0

[fabriziocacicia]

Just by adding

dependencies:
   m4d_components: ^0.1.29

in my pubspec.yaml, I get this message:

Resolving dependencies

Because m4d_components >=0.1.26 depends on m4d_core >=0.2.0 <1.0.0 which depends on l10n ^2.0.0, m4d_components >=0.1.26 requires l10n ^2.0.0.
Because l10n >=2.0.4 depends on analyzer ^0.32.0 and no versions of l10n match >=2.0.0 <2.0.4, l10n >=2.0.0 requires analyzer ^0.32.0.
Thus, m4d_components >=0.1.26 requires analyzer ^0.32.0.
And because angular 5.2.0 depends on analyzer ^0.34.0 and no versions of angular match >5.2.0 <6.0.0, m4d_components >=0.1.26 is incompatible with angular ^5.2.0.
So, because admin_dashboard_web depends on both angular ^5.2.0 and m4d_components 0.1.29, version solving failed.

Process finished with exit code 1

[rfschubert]

Same here... any news?

[MikeMitterer]

Sorry, for the inconvenience. I upgraded l10n and loosened to constraints to analyzer to analyzer: '>=0.32.0 <1.0.0' I think the more you use Dart the more you get into such problems. The dependency hell under Dart is still a big pain in the Ass.

Second thing is that I haven't tested m4d_xxx under Angular at all. m4d_xxx is/was thought as an alternative approach and as such I'm using it internally.

Third thing and to be fair I have to say that I'm currently moving my whole codebase to TS...