Usage with non-default tsconfig config

[bitflut]

Hi, we are happily using db-migrate in an nx mono-repo. When we started using tsconfig-paths, our migrations stopped working. As we have a custom tsconfig we need to point the script to, we tried using: npx ts-config --project tsconfig.migration.ts -r tsconfig-paths/require -r -- node_modules/db-migrate/bin/db-migrate. This still didn't work correctly.

So digging deeper, we found out that db-migrate-plugin-typescript requires ts-node again and this time without configuration. This seems to overwrite whatever we have configured in the command line. By simply forking this repo and commenting out the require, we were able to get things running again.

My questions:

• Do I need to register the .ts extension via a plugin and keep my fork?
• Could this plugin only require ts-node if it was not already registered?

Thank you!

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.