Re: [w3c/webcomponents] HTML Modules (#645)

I know, I am very late in this discussion, but wanted to throw in my opinion on the lost Html Imports:
We have been developing a Web-Application suite for the last three years based on Polymer 1.x. The WebApplication suite's core library contains 230 Custom Elements. When used in an Application of our suite, this makes use of >3000 Html Imports. 
When we decided to start with Polymer 1.x, one key point of the decision was the ability to define a WebComponent in one file, having markup, style and script in one place with the ability to debug all that without a compilation step in between. Of course, it was crucial, that we could import WebComponents inside WebComponents etc. such that we could divide the Application into parts.
As the applications grew, one other important point were dynamic imports, which we need to use for late-loading parts of our applications.

We now have released the first public release of our new application suite and have the time now to plan upgrading our code base from polymer 1.x to some more recent release, like for example Polymer 3.0. 
The question is: Shall we really migrate to something which does not meet our initial requirement of having the markup together with the style and script? What are the alternatives?
This thread lets me hope, that there will be some replacement to the beloved html import sometimes. But how long might this take and how good are the chances that it will even make it into a standard implemented by all browser vendors? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/645#issuecomment-454894771