TC39 Module Harmony
2022-07-20
plaintext logs
prev next
source on github
17:52
<Kris Kowal>
I like the import(..., {xyzkey: "module"}) syntax presented; I think we could use some bikeshedding on the key
I suspect that ljharb’s objection could be resolved by changing the form to import(string, {module: true}) (the name in syntax appears in the options bag)
17:53
<littledan>
ah I like that option
17:53
<Kris Kowal>
And I would be fine with that. reflect is hedging on coherence with assets, which is unknown.
17:53
<littledan>
well, assets could just be a separate key
17:53
<Kris Kowal>
And I’m fine with that too.
17:53
<nicolo-ribaudo>
Or import.module(string), so that the words are also in the same order
17:54
<ljharb>
both of those would address my mirroring constraint yes
17:54
<ljharb>
there's tons of ways to do so; i have no strong opinion on the best way
17:54
<Kris Kowal>
Your constraint is valid.
18:10
<Kris Kowal>
Or import.module(string), so that the words are also in the same order
I would want const myImport = async (...rest) => import(...rest) to be sufficient to drop import from 2nd to 1st class and handle all the things import does, so I’m leaning away from a syntactic solution.