Dependency failure with web_components > 0.10.1

[alexpaluzzi]

Using angular 1.1.0 with any version of web_components greater than version 0.10.1 (such as 0.10.2, 0.10.2+1, and 0.10.3) throws this error:

Pub get failed, [1] Resolving dependencies...
Package collection has no versions that match <empty> derived from:
- angular 1.1.0 depends on version >=0.9.1 <1.0.0
- barback 0.15.2+4 depends on version >=0.9.1 <2.0.0
- glob 1.0.4 depends on version >=1.1.0 <2.0.0

[Zeliret]

[IsNull]

Same here. pub version 1.9.1.

dependencies:
  angular: any
  web_components: any

Leads to the same error message.

Even more strange, if I put this in pubspec:

dependencies:
  angular: any
  web_components: 10.10.1

pub gets stuck in Resolving dependencies... forever. Setting --verbose, will then show that pub seems to be caught in an endless loop, as it over and over again will print the same dependency trees...

[erikreinert]

For anyone still battling this, did a bit of digging and it looks like not much love is being given to Angular for Dart now that Angular2 for Dart is in development. It does look like you can resolve dependency issues using the Angular2 alpha with the latest web_components, etc:

https://pub.dartlang.org/packages/angular2

[IsNull]

Oh i was not even aware that there is angular 2 coming for dart, since they state everywhere that angular for dart is already what angular 2 for js want to become.

Anyway, for my current project I stepped back from the dart world and went for angular 1 with TypeScript... A package manager which gets caught in circular dependencies and cant recover seems daunting for a development environment 😨 I will surely check back when dart with angular 2 is more mature.

[alexpaluzzi]

@IsNull Angular2 is being written with TS that will build down to both JS and Dart versions. It is very much a Dart library as well.

That's also why it's no longer called "angularjs" starting with version 2. :)

[zboralski]

Doesn't seem to be a problem anymore... using pub 1.12.2