imperative imports · Issue #368 · tc39/ecma262

ES2015 specifies a sequentialized evaluation order of modules, where the particular syntactic location of an import statement in a module body has no effect on the order of evaluation. Instead, the semantics simply determines a module's list of direct dependencies and recursively calls ModuleEvaluation() on each of them in order before evaluating the body. I'll refer to this semantics as declarati

[yosuke_furukawa]

ES2015 modules の中で imperative imports つまり、「必ずこのタイミングでは必須のmodule」を決められるための提案。CJSみたいな方式も見込んでの提案なのでNodeとcompatを取るためにもあったほうが良さそう。

[teppeis]

ES6 Modulesの命令的なimportについて

[efcl]

TC39 discuss declarative imports and imperative imports. ES2015 specifies a sequentialized evaluation order of modules. it's well-known as "declarative imports". TC39 consider about top-level await. ## The case for imperative imports - Compatibility with Node - Side effects - Increased expressivity