esno VS ts-node-dev

Love this project, used it quite a bit. However I always opt for using esno[1] instead, merely because of the name; having two tools share the same name throws me off.

[1] https://github.com/esbuild-kit/esno

Next, I thought well nx is not gonna work for now, so let's keep looking for an alternative to ts-node. Oh look, there is this https://github.com/esbuild-kit/tsx. It natively understands path aliases, no need for any flags. Oh wait...it doesn't do any type checking like ts-node. WHAT? why would anyone execute typescript without type checks during development?.

I’ve generally found tsx to be better/less hassle than ts-node

https://github.com/esbuild-kit/tsx

For just running Typescript files you have (both for dev and prod) https://github.com/esbuild-kit/tsx with command is generally easier then using ts-node + some file watcher or compiling to js

Just use tsx: https://github.com/esbuild-kit/tsx

I've been using tsx, which is like ts-node except it uses esbuild under the hood. It's been pretty great. Super speedy.

And compared to esno?

Typescript with TSX for development

Take a look at Typescript runners like ts-node or esno (https://github.com/antfu/esno)

Wait, why are we not using ts-node-dev? Currently, there are some issues related to TS ESM projects that are making its use harder. Check this issue for more details.

Earlier, the sample React project re-transpiled modified TypeScript code during code changes. You can do the same for server-side TypeScript projects with tsc --watch and nodemon or ts-node-dev.

Before switching to the above, I used to use ts-node-dev but it does not support ESM or swc properly.

If you still prefer ts-node then I would highly recommend ts-node-dev which has autoreload included

I personally prefer ts-node-dev over this setup