Skip to Content
📖 Guide DocumentsTTSCOverview

TTSC

The compiler, the runtime, the language server, and the bundler adapter — one toolchain, one plugin contract, one source of truth (tsconfig.json).

npx ttsc           # build · check · watch · fix · format
npx ttsx file.ts   # run TypeScript with a real type-check
npx ttscserver     # LSP host for plugin diagnostics in your editor

In this chapter

  • Compile — ttsc build / check / watch / fix / format. Day-to-day commands and the full flag reference.
  • Execute — ttsx. The typed replacement for tsx and ts-node.
  • Language Server — ttscserver. What the VSCode extension talks to.
  • Bundler integration — @ttsc/unplugin. Same plugin pass inside Vite, Webpack, Rollup, esbuild, Rspack, Rolldown, Next.js, Farm, Bun.
  • tsconfig recipes — common tsconfig.json patterns.

For plugins you can install today — typia, @ttsc/banner, @ttsc/paths, @ttsc/strip — see the Plugins chapter. For @ttsc/lint, see its own chapter at @ttsc/lint.

How they fit together

A ttsc build is one pass over your project:

  1. Read tsconfig.json.
  2. Build the TypeScript-Go Program + Checker.
  3. Run every plugin in compilerOptions.plugins order.
  4. Emit JS + .d.ts (or skip, with --noEmit).

ttsx is the same up to step 3, then executes instead of emitting. ttscserver is the same up to step 3, then proxies diagnostics over LSP. @ttsc/unplugin is the same plugin pass embedded inside a bundler.

You configure plugins once, in tsconfig.json. Every entry point sees them.

Last updated on
📦 SetupCompile