ng4 Quickstart with @vaadin/angular2-polymer - gives error - BrowserDomAdapter

[getnsv]

Hi platosha,

Eager to know when @vaadin/angular2-polymer will be upgraded to support polymer 1 and/or polymer 2. When I build @vaadin with custom fixes for common, core, platform-browser and platform-browser-dynamic, it gives me unable to get BrowserDomAdapter when launched in browser.

Please can you let know when @vaadin/angular2-polymer will get upgraded, or what else I need to customize in the interim.

Please treat this as urgent.

regards, getnsv

[BorntraegerMarc]

Try https://github.com/hotforfeature/origami if you have angular 4+ and polymer 2+

[getnsv]

Thanks Marc for the quick response, but it seems like 'origami' gives only partial support and only few polymer elements. To build a full-fledged mature responsive application you need the rich features of many polymer elements. So is there a roadmap plan to achieve ng4 +polymer 2+ integration with more coverage?

[BorntraegerMarc]

@getnsv what do you mean with partial support?

[hotforfeature]

@getnsv Origami supports all Polymer 2 elements and native custom elements that follow the v1 spec. Out of the box, it should support every single Google #2.0 preview element (far from a few!).

If there's a Polymer 2 feature missing, open an issue on the repo and I'll look at it.

Keep in mind that Polymer 1 elements may not be compatible with Polymer 2 by default. They must be upgraded to hybrid elements.

[flpms]

I think this issue is related. https://github.com/platosha/angular-polymer/issues/146 You've know when this package will be compatible with angular 4?

[jayeshagwan1]

Angular 4 + Polymer 2 not working in IE (Edge,10,9) It gives errors in console and page does not load.

[platosha]

@jayeshagwan1 AFAIK Polymer 2 is IE11+, IE10 and below are not supported.

Also, unfortunately, this library is Polymer 1 only. Please try using https://github.com/hotforfeature/origami instead.