ts-node

[artemdemo]

Hey,

We are absolutely loving using code-migrate in our company, it's been a game changer for us.

But, we've hit a snag. code-migrate currently relies on ts-node to run our TypeScript code, but unfortunately it doesn't come with typescript included. This means we have to manually add it to our toolkit, and that's just not cool.

We have a proposal that we think will take code-migrate to the next level. By replacing ts-node with a runner that doesn't require typescript, such as tsx, we'll be able to streamline our workflow and make our lives so much easier.

wdyt?

[ranyitz]

Thanks for opening this issue!

The initial idea for using ts-node and not providing TypeScript was:

1. performance is not the primary concern when running these migrations, and transpiling the migration code is relatively fast even when it happens on the fly.
2. TypeScript tends to break its API between minor versions and I didn't want to couple the version of code-migrate with the version of TypeScript being used.

---

2 years ago, when this project was created tsx was just a cool idea. by replacing ts-node, we'll be able to get the following benefits:

1. Faster compilation
2. No need to bring TypeScript

The only drawback that I see here is the install size:

• TypeScript + ts-node: 11.6Mb
• tsx: 71.81Mb

Considering the size of code-migrate today (including its dependencies) is: 2.07Mb

This was also a concern when deciding to provide babel instead of swc in vite

---

After considering the install size, we should consider the following options:

1. switch to using babel by default for the transformations - good balance between transpilation time and install time, considering many transpilations use babel anyway
2. Continue to use ts-node by default
3. Enable an option to have a custom transpiler - the migration writer will choose their own transformation logic

@artemdemo what do you think?