Skip to content
This repository has been archived by the owner on Oct 12, 2018. It is now read-only.

Web Components #19

Open
polarity opened this issue May 8, 2014 · 3 comments
Open

Web Components #19

polarity opened this issue May 8, 2014 · 3 comments

Comments

@polarity
Copy link

polarity commented May 8, 2014

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.

@sapegin
Copy link
Owner

sapegin commented May 8, 2014

Do you have any ideas how it could be done in bower-concat? I never use web components.

/cc @artpolikarpov

@polarity
Copy link
Author

polarity commented May 8, 2014

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.

@sapegin
Copy link
Owner

sapegin commented May 8, 2014

Thanks! The fist step should be simple and we can start with it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants