runMigration() fails while importing the migration file using ESM about ts-migrate-mongoose HOT 4 CLOSED

@ilovepixelart I have quickly converted your nestJS example to run in our ESM setup with the same error at service startup: https://github.com/stephan-mitt/ts-express-nest/tree/esm-problem

from ts-migrate-mongoose.

Short answer is no, since transpilation of .ts migration files happens on runtime not compile time, interesting case...
Interesting if swc/register supports esm transpilation

from ts-migrate-mongoose.

@stephan-mitt can you provide a sample repo with minimal setup of nest ESM + ts-migrate-mongoose and how you configured it, so I can run same repo for tests?

from ts-migrate-mongoose.

Spent some time yesterday evening researching this stuff, tried ts-node/register, esbuild-register, @swc-node/register and all of them fail, and found a note on @babel/register:

https://babeljs.io/docs/babel-register
Note: @babel/register does not support compiling native Node.js ES modules on the fly, since currently there is no stable API for intercepting ES modules loading.

Now I'm wondering, how we can approach this if node does not have APIs to do that

from ts-migrate-mongoose.