TC39 Module Harmony on 2023-01-20

08:00	<annevk>	As far as syntax bikeshedding outside of the formal meeting goes, probably don't wanna forget it impacts `import()` too?
08:02	<annevk>	And interesting point on CSS, I didn't realize those would forbid further imports. Not sure if that's enough as they also take URLs, but maybe. (It would have been so nice if import specifiers were just URLs. We could have made `js:specifier` work. Oh well.)
12:41	<littledan>	As far as syntax bikeshedding outside of the formal meeting goes, probably don't wanna forget it impacts `import()` too? Yes, we would need to make the decision of whether this puts all attributes at the top level, or whether they stay in a `with` property
12:42	<littledan>	And interesting point on CSS, I didn't realize those would forbid further imports. Not sure if that's enough as they also take URLs, but maybe. (It would have been so nice if import specifiers were just URLs. We could have made `js:specifier` work. Oh well.) I think it is a straightforward solution to say, within CSS there is a default type (and they would need to add some syntax if they wanted to import JS, whatever that means)
15:01	<Kris Kowal>	Yeah, I will not stop until all URLs are module specifiers and not the other way around ;-)