- From: Ashley (Scirra) <notifications@github.com>
- Date: Tue, 07 Aug 2018 10:58:17 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 7 August 2018 17:58:41 UTC
FWIW I've been keeping this repo relatively up-to-date: https://www.construct.net/blogs/ashleys-blog-2/constructs-effect-compositor-part-1-1024 It could be used as a starting point for implementing something like HTML modules in a JS library. Note however this isn't a polyfill nor is it in any way official or based on any kind of spec. (I have a separate quick-and-dirty polyfill for HTML imports here: https://github.com/AshleyScirra/html-imports-polyfill) However as discussed at https://github.com/AshleyScirra/import-as-and-html-modules/issues/2, my latest thinking is just to use ES modules, and bring in markup and style using something similar to `importAs`. ES modules got there first as "the" module system for web development, and I don't think there's anything to gain by making a parallel one that goes through HTML. -- 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-411146460
Received on Tuesday, 7 August 2018 17:58:41 UTC