You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2018. It is now read-only.
Umm yea, Web Components are on the horizon. There a basically html files including css and js stored as bower components. I am not happy about storing Web Components on bower but yea, thats how it is actually.
Obviously "grunt-bower-concat" fails at trying to concat these components. Any plans of supporting this in the near future? Im trying to come up with a clean workaround today, basically hiding web components from bower-concat and treat them separately via another task or something.
The text was updated successfully, but these errors were encountered:
Me neither. But it´s a w3c spec and coming soon to browsers natively. Chrome is supporting it partially already. So, the first step could be to just exclude web-component packages from the process to avoid errors. One rule is that packages have to be a "web-component" keyword in the manifest so that shouldn´t be too hard.
Second step could be a look at vulcanize. It´s the current cli tool for concatenating Web Components and resolve all its dependencies. Maybe we can just implement it into grunt-bower-concat? Sounds like the easiest way to me.
Umm yea, Web Components are on the horizon. There a basically html files including css and js stored as bower components. I am not happy about storing Web Components on bower but yea, thats how it is actually.
Obviously "grunt-bower-concat" fails at trying to concat these components. Any plans of supporting this in the near future? Im trying to come up with a clean workaround today, basically hiding web components from bower-concat and treat them separately via another task or something.
The text was updated successfully, but these errors were encountered: