3 ms·

The main argument in that post doesn't even hold; using ESM, you can always using dynamic imports: await import( someExpression ) Besides, static analysis a

• jampekka 2y ago
  That forces dynamic imports (and is horrible ergonomics as discussed in the post). CJS requires can be statically analyzed to figure out whether a require can be static, as is done e.g. in all bundlers. ESM import runs side effects as well.
  • 9dev 2y ago
    We have had top-level await for a while now. I don’t know what’s so horrible about this: const app = express() app.use("/users", await import("./routers/users")) …if you’re so inclined to do things exactly as you did in the past. I’m pretty sure bundlers will even transform that into an ordinary module import. The cases where you actually need dynamic imports are few and far between. Are we actually talking about engine limitations here, or is it just a few snowflakes that insist on creating loggers like this? require("debug")("acme") What is so particularly pretty about that is beyond me. > ESM import runs side effects as well. At runtime, yes. Not during static analysis.