4 ms·

From what I have been told, this proposal is likely to win out: https://github.com/tc39/proposal-dynamic-import https://github.com/tc39/proposal-dynamic-import

• mstade 10y ago
  Looks to be a stage 3 proposal[1] so that seems likely. Had a quick read through, looks like a pretty solid proposal. If I read it correctly, it means `import()` will only load ES2015 modules. (I.e. the result of HostResolveImportedModule is a Module Record. That's a good thing as far as I'm concerned. Given the history of discussion around this, this seems surprisingly low key and reasonable. (The System.loader stuff was gnarly!) But what does this mean for nodejs? I don't see how this rhymes with current proposals re `require.import` and the likes. If the above proposal wins out it becomes a language spec, so presumably will also become available in nodejs, and if they go ahead with the ideas mentioned in another comment here, we'd have both `import(specifier)` and `require.import(specifier)` – seems pretty confusing, but maybe I'm getting it all wrong? [1]: https://github.com/tc39/proposals https://github.com/tc39/proposals