esno VS ni

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)

this is awesome! how would you contrast this with https://github.com/antfu-collective/ni?

View on GitHub

Repo: https://github.com/antfu/ni

Here's a description of all currently supported commands. In case something changes and this gets outdated, you can always check the full list on the project's README.

I highly recommend using https://github.com/antfu/ni to not care about if the project uses npm/yarn/pnpm

By using ni, you can save yourself a lot of time and avoid the frustration of dealing with conflicting lock files and dependencies. So if you haven't already, give ni a try — you won't regret it!

You might want take a look at ni by antfu: https://github.com/antfu/ni