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

@snuggs, no, I was just expanding on what was posted here.

> The original ES6 module syntax requires that all import statement should be statically parsable without evaluation

@TakayoshiKochi, I'm no an expert there either but I bet the syntax here would work if the same restrictions imposed on `export` statements in modules currently also applied to their use in the body of an inline module. Also, I think they would need some way to reference one inline module from another without nesting. If they only supported trees then they wouldn't support everything that per-file modules do and wouldn't make for a useful build target. (Assuming that's their primary use case, maybe not?)

-- 
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-311474926