Skip "default" export from export * from "mod"

[jdalton]

I noticed while reviewing our export extension proposals that by spec we should not export "default" for export * from "mod".

See https://tc39.github.io/ecma262/#sec-getexportednames.
Also mentioned in step 6 of https://tc39.github.io/ecma262/#sec-resolveexport.

This effects runtime.makeNsSetter.

[benjamn]

I agree this is what the spec says, but I'm having trouble understanding why this is desirable behavior, because this breaks the ES equivalent of module.exports = require("./other-module") (the CommonJS "bridge" idiom). I think this is something we need to bring up at TC39.

[benjamn]

Yeah, this seems inconsistent with the creation of module namespace objects, which uses GetExportedNames: https://tc39.github.io/ecma262/#sec-getmodulenamespace

Imagine if a dynamic import(...) couldn't access the default property of the imported module!

[benjamn]

Okay, I've opened an issue on the tc39/ecma262 repository. Looking forward to understanding this policy better, or getting it retracted!

[jdalton]

Thanks for raising this with the TC39.