Unexpected `top-level await error` for `type: module` + top level await in `node_modules` about tsx HOT 1 OPEN

Thanks for the bug report @JounQin

tsx supports loading ESM in Node's CommonJS mode by compiling it to CommonJS syntax... so if a module file (.mjs or package.json#type: 'module') gets require()'d, it gets converted to CommonJS. Since require() is sync, it cannot handle top-level await. Basically, this is the same limitation as the recent improvement in Node: nodejs/node#51977

Looking at Prettier's code, it looks like it tries require() first, and if it fails, it tries import(). Because we want it to go to import() (which supports TLA), you can opt-in only to the ESM enhancement:

node --import tsx/esm scripts/test

This way, the require() will fail, and skip to the import() and the TLA file will get loaded expectedly.

Since it catches the ERR_REQUIRE_ESM error, it might be a good idea to make tsx emit that instead of or in addition to the TLA error.

By the way, if you have any sway in how Prettier loads the config files, the new tsImport() function might be useful for supporting TypeScript configs.

It's being experimented in ESLint via eslint/eslint#18440

from tsx.