[feat]: Don't panic `ERR_REQUIRE_ASYNC_MODULE` when using try/catch approach, it should thrown only when top `await` executed

[JounQin]

What is the problem this feature will solve?

/** @type {Plugin[]} */
let plugins

try {
  plugins = dependencies.map(pkgName => {
    /** @type {Plugin} */
    const pkg = require(pkgName)
    return pkg.default || pkg
  })
} catch {
  plugins = await Promise.all(
    dependencies.map(async pkgName => {
      /** @type {Plugin} */
      const pkg = await import(pkgName)
      return pkg.default || pkg
    }),
  )
}

What is the feature you are proposing to solve the problem?

I'd like to use require(ESM) when possible but fallback to top await when it fails.

What alternatives have you considered?

N/A

[joyeecheung]

require() does execution, so when ERR_REQUIRE_ASYNC_MODULE is thrown, it's already about to execute the top-level await. I think in the snippet above you probably don't want the code containing top-level await to be executed twice, which is what the proposal would lead to? Also I think the current behavior already works with the snippet above, if not please provide a more concrete reproduction that can be run.

[JounQin]

@joyeecheung Glad to hear it should be supported, I'll add a small repo ASAP.

[JounQin]

Not sure why, but it's working as expected now: 1stG/configs#362, so closing