
Vercel Labs just shipped scriptc — an experimental compiler that turns TypeScript directly into a self-contained native binary. No Node. No V8. No JavaScript runtime in the output. Startup clocks at 1.78ms, the binary weighs 370KB, and idle memory sits at 1.9MB. Those numbers are real. The caveats are also real, and you should know both before you commit to anything.
What scriptc Actually Does
scriptc uses the real TypeScript compiler for parsing and type-checking, then lowers your code to a typed intermediate representation and emits either LLVM IR, C, native assembly, or WebAssembly (WASI Preview 1). The result is a standalone binary your target machine can run without installing anything.
The project uses a three-tier compilation model. Most plain TypeScript code gets compiled natively. npm packages and dynamically-typed constructs fall back to an embedded quickjs-ng engine (~620KB). Everything else gets rejected at compile time with an error code and a rewrite hint. That last category is where most npm packages land.
The Numbers — Both the Good and the Ugly
The startup and memory benchmarks for scriptc 0.0.16 against Bun 1.3.12 and Node 24.18.0 are genuinely striking:
| scriptc | Bun | Node 24 | |
|---|---|---|---|
| CLI startup | 1.78ms | 21.29ms | 61.78ms |
| Binary size | 370KB | 60MB | N/A |
| Idle memory | 1.9MB | — | 181MB |
Now the part that changes the calculus: execution throughput is approximately 7.5x slower than Node 24. That trade-off is fundamental to the architecture. You get instant startup and tiny binaries at the cost of raw compute performance. For a CLI tool that starts, does something small, and exits, that is a perfectly reasonable bargain. For a web server handling hundreds of requests per second, it is not.
Who Should Actually Try This
scriptc is built for a specific niche: TypeScript projects with minimal or zero npm dependencies that need to ship as a single executable. The sweet spot is internal CLI tools, DevOps automation scripts, and small utilities you want to distribute to machines that do not have Node installed. If your project relies on npm packages for anything meaningful, expect most of them to be rejected at compile time.
Bun’s compile mode produces 60MB binaries but handles the full npm ecosystem and performs at Node-level throughput. If you need broad compatibility, Bun wins. If you need a 370KB binary that starts in under two milliseconds and ships with zero dependencies, scriptc is the only option in the TypeScript ecosystem right now.
The Concern Worth Taking Seriously
Vercel Labs shipped zerolang in August 2026 — a graph-first language designed for AI agents. It went dormant weeks after launch. The Hacker News thread for scriptc is full of people drawing that comparison, and they are not wrong to. One commenter called the architecture "idiotic" and the performance claims "zero credible." A real-world tester reported hundreds of compile errors on actual projects. Simon Willison pushed back, noting that building "small, fast binaries without writing Rust" is a genuine capability gap scriptc fills.
Both views are correct. The benchmarks are real but narrow. The longevity concern is real but speculative. The npm compatibility wall is real and immediate.
Getting Started
scriptc requires Clang and Node 24 or newer. Install it, compile a TypeScript file, run the output:
npm install -g scriptc
scriptc build hello.ts
./hello
The project is Apache 2.0 licensed and available on GitHub. Current version is 0.0.16. The InfoQ deep-dive covers the compilation pipeline in detail. Check the hands-on real-world test before investing serious time — the honest results will help you set the right expectations.
scriptc is worth watching if you build CLI tools in TypeScript. It is not worth betting a production deployment on, not yet. Try it on a throwaway script first — the install takes thirty seconds and the startup time genuinely will impress you.

