tsx vs tsc vs ts-node

Pick the right TypeScript toolchain per environment - tsx for fast dev and tests, tsc for production dist/, and avoid new ts-node adoption unless brownfield constraints require it.

Recipe

{
  "scripts": {
    "dev": "node --watch --import tsx src/main.ts",
    "build": "tsc -p tsconfig.json",
    "start": "node dist/main.js",
    "test": "node --import tsx --test src/**/*.test.ts"
  },
  "devDependencies": {
    "typescript": "^5.6.0",
    "tsx": "^4.0.0",
    "@types/node": "^24.0.0"
  }
}

When to reach for this:

• Bootstrapping a new Express 5 or Fastify 5 service
• Choosing CI commands that mirror production
• Replacing ts-node-dev or nodemon + ts-node stacks
• Debugging "works with tsx, fails with node dist" mismatches

Working Example

// src/main.ts
import { createServer } from 'node:http';
 
const port = Number(process.env.PORT ?? 3000);
 
createServer((_req, res) => {
  res.end('ok');
}).

# Development - no separate compile step
npm run dev
 
# Production pipeline
npm run build
npm run start

// tsconfig.json - emit for production
{
  "compilerOptions": {
    "module": "NodeNext",
    "moduleResolution": "NodeNext",
    "outDir": "dist",
    "rootDir": "src",
    "declaration": true,
    "sourceMap": true,

What this demonstrates:

• tsx hooks Node's loader - transforms TS on the fly via esbuild
• tsc writes dist/main.js preserving ESM import specifiers with .js extensions
• Production runs plain node - no devDependency loader in the container
• --watch + tsx replaces nodemon for many services

Deep Dive

How It Works

• tsx - esbuild transform, fast startup, supports ESM and import.meta, ideal for dev/test.
• tsc - full typecheck + emit; slower but authoritative for declarations and dist/.
• ts-node - older on-the-fly compiler integration; ESM support more finicky than tsx.
• tsc --noEmit - typecheck-only CI job without emit - pairs with build job.

Pipeline Comparison

TypeScript Notes

{
  "scripts": {
    "typecheck": "tsc --noEmit",
    "dev": "node --watch --import tsx src/main.ts"
  }
}

Run typecheck in CI even when dev uses tsx - tsx alone skips type errors.

Gotchas

• Shipping tsx to production - adds devDependency surface and transform overhead. Fix: node dist/main.js in Docker CMD.
• tsx passes type errors - transpile-only. Fix: tsc --noEmit in CI gate.
• Path aliases without emit support - tsc does not rewrite paths. Fix: NodeNext relative imports or tsc-alias post-step.
• Different module output (CJS vs ESM) - tsx runs source; tsc emits per module. Fix: align package.json "type" with emit.
• Keeping ts-node for ESM in 2026 - harder config than tsx. Fix: migrate dev scripts to node --import tsx.

Alternatives

FAQs

Related

• TypeScript in Node Basics - tsconfig defaults
• Gradual Typing Brownfield - migrating JS codebases
• Typecheck in CI - gate merges
• Running Scripts & Shebang - npm scripts

Stack versions: This page was written for Node.js 24.18.0 (Active LTS), npm 10+, TypeScript 5.6+, Express 5, Fastify 5, and NestJS 11.