> There's just no way anymore to directly combine an import statement with some other JS syntax, whether or not the module path is statically specified. I alwa

> There's just no way anymore to directly combine an import statement with some other JS syntax, whether or not the module path is statically specified. I always found this to be an anti-pattern that I tried to avoid, it felt way too “cute”. I won’t pretend the switch to ESM has been completely smooth but it does feel like the better way to pull in dependencies. It reads better IMHO and makes more sense to me.