web_components as a dependency

[vicb]

I'm wondering if "web_components" shouldn't be listed in the dev_dependencies rather than dependencies in the pubspec.yaml.

We're only using it for tests / examples.

[kemallette]

Yes please! Alternatively, loosening the constraints if possible would be very helpful. Today, I tried experimenting with the new paper elements lib and could not install due to the web_components dependency.

Pub get produced:

Pub get failed, [1] Resolving dependencies... (2.2s)
Package web_components has no versions that match <empty> derived from:
- angular 0.12.0 depends on version >=0.3.3 <0.4.0
- core_elements 0.0.6 depends on version >=0.4.0 <0.5.0

[michilu]

I got an inconsistence of dependency when use AngularDart with paper_elements.
paper_elements: https://github.com/dart-lang/paper-elements

Package web_components has no versions that match <empty> derived from:
- angular 0.13.0 depends on version >=0.3.3 <0.4.0
- core_elements 0.0.6 depends on version >=0.4.0 <0.5.0

[vicb]

Actually WebPlatform makes calls to platform.js so I think that having web_components as a dependency makes more sense.

We should probably probably have a looser constraint though.

If you need a newer version, you can override this dependency in your pubspec.yzml as a workaround for now.

[michilu]

@vicb OK, Thanks! I will try it.

[vicb]

@michilu FYI, @jbdeboer has been working on improving the support for custom components (see the paper example) and @vsavkin is also looking at some problems with have with the shims for browsers that do no support web components.
Don't expect everything to work flawlessly for now but things are improving.