mikro-orm: Cannot use v5.4.0 with ts-node on Node v16

Describe the bug After upgrading to v5.4.0 I can no longer run npx mikro-orm debug (or use it in any other way) if ts-node is involved. It has something to do with how dynamic imports are handled now.

I did make it work tho by running it like this:

node_modules/.bin/ts-node-esm node_modules/@mikro-orm/cli/cli debug

also like this (when running my app, not the mikro-orm’s CLI itself):

node --inspect=0.0.0.0:9229 --loader ts-node/esm bootstrap.ts

Prior to the upgrade, it did work out of the box. Everything seems to be fine outside the ts-node’s context (e.g. when running compiled JS).

CLI

npx mikro-orm debug 
Current MikroORM CLI configuration
 - dependencies:
   - mikro-orm 5.4.0
   - node 16.17.0
   - typescript 4.6.4
 - package.json found
 - ts-node enabled
 - searched config paths:
   - /path/to/my/project/config/mikro-orm.config.override.ts (not found)
   - /path/to/my/project/config/mikro-orm.config.ts (found)
   - /path/to/my/project/config/mikro-orm.config.js (not found)
   - /path/to/my/project/mikro-orm.config.ts (not found)
   - /path/to/my/project/mikro-orm.config.js (not found)
- configuration not found (Unknown file extension ".ts" for /path/to/my/project/config/mikro-orm.config.ts)

tsconfig.json

{
    "compilerOptions": {
      "target": "es2021",                       /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017','ES2018' or 'ESNEXT'. */
      "module": "commonjs",                     /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */
      "lib": ["es2021", "DOM"],                 /* Specify library files to be included in the compilation. */
      "declaration": true,                      /* Generates corresponding '.d.ts' file. */
      "sourceMap": true,                        /* Generates corresponding '.map' file. */
       "outDir": "build",                       /* Redirect output structure to the directory. */
      "strict": true,                           /* Enable all strict type-checking options. */
       "strictPropertyInitialization": false,  /* Enable strict checking of property initialization in classes. */
       "alwaysStrict": true,                  /* Parse in strict mode and emit "use strict" for each source file. */
       "noUnusedLocals": true,                /* Report errors on unused locals. */
       "noUnusedParameters": true,            /* Report errors on unused parameters. */
       "noImplicitReturns": true,             /* Report error when not all code paths in function return a value. */
       "noFallthroughCasesInSwitch": true,    /* Report errors for fallthrough cases in switch statement. */
      "moduleResolution": "node",               /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
      "rootDirs": [                             /* List of root folders whose combined content represents the structure of the project at runtime. */
      ],
      "types": [                                /* Type declaration files to be included in compilation. */
          "node",
          "mocha"
      ],
      "esModuleInterop": true,                  /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
      "experimentalDecorators": true,           /* Enables experimental support for ES7 decorators. */
      "emitDecoratorMetadata": true,            /* Enables experimental support for emitting type metadata for decorators. */
      "resolveJsonModule": true,
      "forceConsistentCasingInFileNames": true
    }
  }
  

Additional context I’m not actually using ESM in my app. This app remembers NodeJS v8 😃

Versions

Dependency	Version
node	16.17.0
typescript	4.6.4
mikro-orm	5.4.0
your-driver	MySQL