Esm: consider implementing "export namespace from" [proposal]
https://github.com/tc39/proposal-export-ns-from (I guess it's not really a proposal anymore, but rather an addition)
related to: https://github.com/standard-things/esm/issues/495
@jdalton since you are also involved in this "proposal" I thought it would be a good idea to spearheading this and add it to esm :blush:
it seems there's pretty much consensus in the committee: https://github.com/tc39/tc39-notes/blob/master/es9/2018-05/may-22.md#9ib-normative-add-export--as-ns-from-mod-to-export-production-and-module-semantics and they are waiting for implementers.
If implemented, I think this wouldn't even need to go behind a flag (similar to dynamic import and import.meta, stage 3)
dnalborczyk
All 4 comments
Yeah, this is a good thing to add support for.
Update:
Welcome new core maintainer @dnalborczyk!
If you're up for tackling this the areas to tweak would be
- src/acorn/parser/import.js
- src/visitor/import-export.js
- test/export-tests.mjs
- maybe test/compiler-tests.mjs
Update:
From the TC39 meeting this week @leobalter requested implementers take a swing at supporting this, so we can do our part there too.
jdalton
on 5 Jul 2018
Cool! Do we have this on esm?
damianobarbati
on 22 Aug 2018
@damianobarbati Not yet.
jdalton
on 22 Aug 2018
I've got this working locally.
Still ironing out an unrelated bug that surfaced as part of the unit tests for this.
Update
Bugs are now ironed out :tada:
jdalton
on 24 Oct 2018
Related issues
Pokute
路
3Comments
janusqa
路
3Comments
MVSICA-FICTA
路
3Comments
pvdlg
路
3Comments
StphamZ
路
3Comments
Most helpful comment
Yeah, this is a good thing to add support for.
Update:
Welcome new core maintainer @dnalborczyk!
If you're up for tackling this the areas to tweak would be
Update:
From the TC39 meeting this week @leobalter requested implementers take a swing at supporting this, so we can do our part there too.