I’m currently jumping on the webcomponents train, I’m converting all my app’s code to webcomponents (with Polymer) and only use meteor’s template features where it makes sense. Now I’m wondering how should we approach writing maintainable components in the future with webcomponents in mind. There are essentially three options:
1.) Just use packages for certain features/wrapping APIs
2.) Use packages and use those wrapped functions in a custom element
3.) Use no packages and wrap the API with a custom element
Number three has the upside of being easily shareable between future/other custom elements (keyword composability), ensuring that not only meteor developers can make use of those components but instead pretty much every web developer, making those elements and wrappers more interopable with other frameworks and vice/versa.
What are your thoughts on this topic? What is MDGs standpoint on webcomponents and how to use them? 1-2 months from now someone said Polymer isn’t being integrated because it’s not production ready. With a polyfill for dom-manipulating frameworks on the horizon and all major browser vendors having started to implement the finalized shadow DOM v1 specs it would be interesting to hear how we will deal with these things.