tsx

how does it compare to tsx ? https://github.com/privatenumber/tsx

For those looking for an alternative no-compilation TypeScript runner, I'm quite satisfied with TSX: https://github.com/privatenumber/tsx Node.js itself is getting quite close to running TypeScript natively, but they don't support using ES imports of CJS packages and importing with no-extension qualifier.

I like tsx for this, and it's actively maintained. The author may not know about it. https://github.com/privatenumber/tsx

or you could do what tsx does? charge money to fix issues as an option https://github.com/privatenumber/tsx/issues/758 issues are fixed on priority basis for people willing to pay

It doesn’t. The comment you’re replying to is referring to tsx, the package that lets you execute ts files, not to running files with the tsx extension. https://github.com/privatenumber/tsx

btw if anyone is looking to run ts on node, there is tsx. there is also ts-node but i prefer tsx. https://github.com/privatenumber/tsx

Appreciate this change. The ESM stuff is nightmarishly esoteric. Most recently I ran into ERR_REQUIRE_ESM while trying to write Playwright E2E tests that import from other packages in our monorepo. I really think the way ESM was handled hurt Node.js a lot. Couple this with the introduction of TypeScript and complexity in the Node.js ecosystem skyrocketed. I've lost so many hours on this. Thankfully libraries like esbuild exist (and by extension `tsx` which uses esbuild under the hood). https://github.com/privatenumber/tsx

> you have to deep-dive into different frameworks, different tools that all do the same thing You can also just choose one language/tool/framework and do _everything_ in it. I know this might get snubbed, but you can do almost anything these days with TypeScript. It can be as typed or dynamic as you want it (well sort of), plays well with UI/web/react, server with node, has pretty good performance these days, and you can even easily run CLI scripts with tsx. `#!/usr/bin/env tsx` (https://github.com/privatenumber/tsx)

I really enjoy frontend/node/typescript development. I roll my eyes whenever the HN-types complain about CSS or frontend development being a hellhole. Mostly the comments I see seem ignorant or impatient ("Why doesn't this thing work without be bothering to learn it?") However, the intersection of typescript, nodejs, and ES modules is consistently the most frustrating experience I ever have. Trying to figure out which magic incantation of tsconfig/esbuild/tsc/node options will let me just write code and run it is a fools errand. You might figure something out, and then you try to use Jest and then you descend into madness again. The biggest tip I can give people is to ditch ts-node and just use (the awkwardly named) tsx https://github.com/privatenumber/tsx, which pretty much just "mostly works" for running Typescript during dev for node.

this setup doesn’t work with node test runner. I had to tsc then node --test the built files. tsx also is missing the test runner https://github.com/privatenumber/tsx/issues/257

I’ve found TSX to be a better alternative to ts-node. It seems to have more sensible defaults in 2023. https://github.com/privatenumber/tsx

I’ve generally found tsx to be better/less hassle than ts-node https://github.com/esbuild-kit/tsx

Have a look at https://github.com/esbuild-kit/tsx tsx is a CLI command (alternative to node) for seamlessly running TypeScript & ESM, in both commonjs & module package types. It's powered by esbuild so it's insanely fast. I also suggest using its alias: esno