Caridy Patiño
Caridy Patiño
@jonco3 confirmed! you're right. we will try to fix this issue soon.
yeah. I suspect that the default loader implemented in each engine will support `json`, but we haven't get to define that just yet.
I'm not sure yet if this is important or not, without thinking too much about it, I think parity is important because we don't want to attempt fetching an already...
### Update `[[Metadata]]` is an internal slot on ModuleStatus objects (registry entries), but as today, there is no way to set them, and no way to inspect them, we could...
this is going to be very tricky because we don't know what to share.
@nlwillia you have the fetch hook, and you can do your own fetching, and keep your own cache. On top of that, we have the module status metadata, which will...
To clarify, or to raise the question, depending on how you look at this, but `local.import("./foo.js").then(def => ...)` is really not reflective as it is the current proposal, essentially because...
> Not having to say default explicitly is very important to the ergonomics. Yes > It's extremely rare to mutate top-level exports after that point. Agree. We can probably make...
jejeje, `importAll` resonates well with me considering the work we have done on https://github.com/estree/estree/blob/master/es6.md#exportalldeclaration, which is symmetrical to the import all concept. I like it. still we should clarify whether...
@johnjbarton nobody will do `import { default as foo } from './foo.js';`, they will do `import foo from './foo.js';` that's the whole point @dherman is trying to make, you should...