(Hypothetically there might have been a place and time in CJS history to force CJS require() to always return a promise and module.exports to always take a function that returns a promise and that hypothetical version might have been compatible enough to import directly from ESM. Nobody actually wanted that hypothetical "ACJS" so it never existed. ACJS could have at least met browsers half-way and might have made the transition less overall painful.)
Having said that, the fact remains that vast majority of pain points that people who actually need to maintain isomorphic libraries face today have nothing to do with synchronous vs asynchronous nature of cjs and esm modules.
It is the myriad pointless nuances like default export, namespace imports etc. that are sources of biggest headaches in day to day work. In cjs there is a simple model that a module exports an object and while importing you import that object. Instead now we have a situation where we need to deal with:
export default {
foo() {...}
}
is not same as: export function foo() { ... }
and import Foo from "foo"
is something different from import * as Foo from "foo"
Plus the additional complexities introduced by import bindings being live etc. are just annoyances that one has to deal with over and over again every time module interop is involved.
What I am saying is that
import Foo from "foo"
could be sematically equivalent to
const Foo = require("foo")
and
const Foo = await import("foo")
could be semantically equivalent to
const Foo = await Promise.resolve(() => require("foo"))
if tc39 designed ESM import spec with CJS compat in mind.
It is fully possible to introduce additional syntax while not breaking the ecosystem.