Allow configuring jiti

[osdiab]

Description

I upgraded from an ancient version of node-pg-migrate to the latest version, which is fine but was using swc to handle typescript migrations before. With that I could configure it to respect tsconfig paths. But now with the jiti tool chain I don’t see an obvious way to configure node-pg-migrate to use tsconfig paths. But I did see that jiti has support for it.

Suggested solution

Provide a way for node-pg-migrate users to configure the underlying jiti config to allow for things like tsconfig paths support.

Alternative

No response

Additional context

No response

[brenoepics]

Hmm, I think we discussed this before at #1460 (comment), but we didn’t see any use case for it at the time. Also, Jiti added support for choosing tsconfig path 2 months ago (unjs/jiti#427), so we didn’t have this option back then. I’d be happy to add it, I can’t really see another way to set the tsconfig path.

[Shinigami92]

I will bring the repo up to date today, then one of you can open a PR for jiti tsconfig path support.
There might be plans that jiti wont be required anymore with v10, but I think bringing it into v9 is still worth it.

[brenoepics]

I will bring the repo up to date today, then one of you can open a PR for jiti tsconfig path support. There might be plans that jiti wont be required anymore with v10, but I think bringing it into v9 is still worth it.

Yeah, I had this in mind when adding Jiti. I haven’t looked into it deeply, but Node.js now has built-in TypeScript support (type stripping). However, I think this issue might regret if we rely on Node 26+, since it only strips types instead of providing full runtime support. So I'd assume features like tsconfig paths, baseUrl, transformers... wouldn’t work for user migration files?