Scriptc by Vercel
Ranked 2 of 6 TypeScript compilers by recommenders
A free TypeScript-to-native compiler that builds small single binaries without a JavaScript engine, though critics doubt its maturity and performance.
A free TypeScript-to-native compiler that builds small single binaries without a JavaScript engine, though critics doubt its maturity and performance.
33 people gave an opinion
- recommend it
- 12
- criticize it
- 21
- approval share
- 36%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 12 people recommend itNeeds 10 or more, met.
- 0.5 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Small static native binaries
“with a single static native binary that does not include the whole Node runtime”
Comment from 27 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary” “Being able to build small, fast binaries without writing them in C or Rust”
Comment from 27 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary” “deploy it as a small single native binary”
Comment from 28 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary”
What people warn about
Each mark is one comment
Largely AI-generated, unclear expertise
“it looks like 99% was vibe-coded by 1 person, and it does not look like they have any compilers background”
Comment from 27 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary” “It's difficult to ignore how the README is filled with Claudisms.”
Comment from 27 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary” “This project reeks of weapons grade AI psychosis”
Comment from 27 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary” Limited coverage, bails out to JS engine
“For every single of them the coverage generates hundreds of errors and so it is basically useless.”
Comment from 27 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary” “For anything else it bails out and asks you to ship a JS engine”
Comment from 27 Jul 2026 in “Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary”
Other TypeScript compilers people recommend
The four most recommended other TypeScript compilers, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| tsgo | 16 | 3 | 84% | 7 | — | Approved |
| Scriptc by VercelThis page | 12 | 21 | 36% | 2 | — | — |
| Perry TypeScript compiler | 11 | 15 | 42% | 4 | — | — |
| tsz | 6 | 3 | 67% | 2 | — | — |
| tsc-ts | 6 | 1 | 86% | 1 | — | — |
What people said
33 of the 38 comments that mention it, newest first. Each links to the original comment.
“it will also work in regular JavaScript runtimes, for free”
“it even diverges from ts semantics in sneaky ways to facilitate its optimizations”
“it doesn't work with this code at present”
“As it stands, the project's direction feels a bit odd.”
“deploy it as a small single native binary”
“is about 7.5x slower than Node 24, even after Claude tried making some scriptc-specific optimizations”
“For every single of them the coverage generates hundreds of errors and so it is basically useless.”
“optionally bundles a 620KB quickjs runtime”
“solves no one's issue and will stop being maintained in a few months”
“seems to be entirely vibecoded”
“Not glamorous but it works”
“A compiler that works only on macOS?”
“with a single static native binary that does not include the whole Node runtime”
“the only viable reason for these kind of projects I see is getting attention”
“I would use it for a focused command-line tool that needs to share code with a larger TypeScript project”
“the architect seems sane, it fits a niche”
“until this is of practical use it will be s long thorny way”
“it looks like 99% was vibe-coded by 1 person, and it does not look like they have any compilers background”
“This look very promising.”
“I can't think of any serious company or project that would use this thing.”
“For anything else it bails out and asks you to ship a JS engine”
“900k lines of code plus tons of deps for a compiler? Does that really make sense to you?”
“Imagine if bridges, skyscrapers, dams, cars, airplanes were designed and built like that.”
“slopped together, hyped up on twitter and then left to be forgotten about”
“The floats rather than integers thing does look bad though.”
“more human effort is going into defending this project then what was put into the project itself”
“wish it was the other way around”
“Their approach to numbers is broken. Their approach to measurement is broken.”
“Being able to build small, fast binaries without writing them in C or Rust”
“aislop code any day of the month”
“This project reeks of weapons grade AI psychosis”
“the architecture is idiotic”
“It's difficult to ignore how the README is filled with Claudisms.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.