ts-node improvements for ava projects?

I came across https://github.com/avajs/ava/issues/1109 which lists several criticisms of ts-node and predates some recent improvements.
For example, ts-node has since implemented an ESM loader which I believe can handle #5.
#20 -- source-map-support -- is enabled out-of-the-box in ts-node.
We allow all configuration to be placed in your tsconfig.json.
And we have an `swc` integration that will be in the next release, allowing users to opt-in to much faster compilation than we can get with babel or typescript.

All that to say, if you have time, I would love to talk about any other bugs , limitations, or inconveniences that your users hit with ts-node. At the very least it will give me some useful data points for improving ts-node. A big goal of mine is to make TS and node tooling feel cleaner, easier, and require less boilerplate.

If you have any thoughts, please let me know.

The issue asks for feedback on ts-node integration in AVA projects and names no files, tests, or entry points. First gather concrete bugs, limitations, or inconveniences from AVA users; done is a specific, agreed improvement rather than general discussion.

Written by the indexing model from the issue text.