Rationale for dropping ModuleImport syntax?
forbes at lindesay.co.uk
Wed Jun 11 07:47:40 PDT 2014
> I really just want single exports and destructuring of single exports...??
I would second that. I have seen no desire for any static analysis beyond "this module depends on that module" and I've seen no desire for live bound imports.
I accept that we're messing with a fragile consensus, but the removal of ModuleImport syntax has already done that, so we're way beyond purely cosmetic changes. I think if this is done wrong it will just do more harm than good, and further fragment the ecosystem. We need something that makes the upgrade path for CommonJS users really simple and clear.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss