Guy Bedford

@mcollina on that note I've always wondered why Node.js doesn't support source maps natively? http://npmjs.org/package/source-map-support is incredibly widely used and seems a straightforward approach to adopt natively. Would be interested...

This is odd as I've had `"type"` in use in the SystemJS repo for some time and haven't had any issues at all there... perhaps it is only for packages...

The API needs more work, but overall these seem like positive directions. One approach might also be to just start simple - I don't think anyone would reject exposing `isBareSpecifier`....

This might also be beneficial to syncify some loader hooks. For example it is seeming more and more likely Chromium wants to ship a synchronous `import.meta.resolve` while Node.js has an...

Right, I was always personally hopeful for an async resolve hook because of the possibility of dynamic resolution, which could seem important not to rule out. It's at a little...

Yes, this proposal could definitely capture asset reflection in that sense, where for that type of reflection non-eager loading could be defined within that if desired. I wasn't aware of...

@bmeck so it is not necessarily a security requirement but more about deferred loading as well as deferred execution in this case? So that you are effectively looking to provide...

One possibility here is that when module blocks are specified, they enable opaque references to uninstantiated modules to be provided to eg worker boundaries. Alongside module blocks it could be...

@Jack-Works see discussion in https://github.com/lucacasonato/proposal-evaluator-attributes/issues/6, as much as possible we want evaluator attributes to alter the "module representation in JS" not the "module instantiation interpretation".

Agreed it is critical to define evaluator attributes as altering module representation or abstraction level in the JS import API, and not the underlying loaded module syntax interpretation. Eg for...