Skip to main content

One post tagged with "migrate"

View All Tags

We retired tsc on our JavaScript packages — and the gate got sharper

· 5 min read
Nudo Contributors
Nudo maintainers

The tsc --noEmit line on your JavaScript packages can retire. Start with zero annotations, add contracts only where you accept them, read violations as value ⊭ predicate + a next step — and exit through migrate retire, not by dual-running two compilers forever.

Most teams keep tsc --noEmit around not because they enjoy writing annotations, but because there was no other CI gate to reach for. Nudo's answer is not "write a second type language". It is three commitments:

  1. JS stays JS — no runtime changes, no invented second IR.
  2. Contracts on demand — *.nudo.js / @nudo:contract; obligations only come from declarations you accept.
  3. A one-way door — nudo migrate status → strip → verify → retire. The exit is retire tsc, not dual-run.

We pinned this story with three runnable samples, not slides: a public checkout-demo, and two real npm consumers.