Skip to main content

Nudo vs TypeScript — when a JS-first gate is the right tool

· 2 min read
Nudo Contributors
Nudo maintainers

Launch series (3/5) — published together on 2026-09-21. Read in order: Day 0 — observe JavaScript without rewriting it · Contracts are JS — Day 1 with sidecar *.nudo.js · Nudo vs TypeScript — when a JS-first gate is the right tool · Nudo for coding agents — agents.md, agent integration, stable diagnostics · The 22-file smear: how call-site attribution almost shipped fake precision

Honest positioning: Nudo is built to replace TypeScript as the day-to-day type gate for JavaScript-first codebases — not to reimplement the TypeScript compiler.

TypeScriptNudo
Primary surface.ts + annotationsPlain .js
ContractsType language*.nudo.js builders + @nudo:contract
InferenceFrom annotationsFrom executing code on Abs
CI gatetsc --noEmitnudo check
.d.tsThe modelA lossy projection of Abs

Prefer Nudo when​

  • The package is JavaScript-first and you refuse a second IR just to get types
  • Behavior (branches, string algebra, loops, bounds) matters more than declared interfaces
  • You want runtime-shaped obligations in CI without body-AST slot invention

Keep TypeScript primary when​

  • The codebase is .ts-first
  • You need the full TS type language as programming
  • Your ecosystem is DefinitelyTyped / project references

Coexistence​

Split by package: JS packages on Nudo LSP + nudo check; TS packages on tsc. See coexistence and limits.

Full map: Nudo vs TypeScript · Migrate from TS.