February 20, 2026
TypeScript goes native—cue the popcorn
Show HN: Write native binary web apps with TypeScript and Express
One‑file web apps in TypeScript—early nods and watch‑this‑space
TLDR: Tsonic’s express-like tool lets you build web servers in TypeScript and ship them as a single native app, powered by .NET 10. Early response is a cautious thumbs‑up with a curator’s nod, while questions loom about the .NET requirement and how closely it matches classic Express behavior—watch this space.
Developers just got a curveball: Tsonic’s new @tsonic/express promises Express‑style code in TypeScript that compiles down to a single native app. Translation for non‑devs: build a tiny website server and ship it as one file—no sprawling setup. That pitch alone had onlookers hovering over the “star” button.
So far, the vibe is cautious curiosity. Early mover orta called it “interesting” and quickly filed it into his curated awesome TypeScript‑derived languages, a quiet but powerful signal boost that says: “worth watching.” Behind the applause, questions are already lining up. There’s a required .NET 10 install—unexpected for the JavaScript crowd—and the docs openly list “known compatibility gaps,” hinting that not every Express trick will work exactly the same. Cue the “is it really Express if it’s not Express?” eyebrow raises.
No fireworks yet—this thread is still pre‑popcorn—but the stakes are clear. Fans love the “write once, ship one binary” simplicity; skeptics will poke at setup friction and real‑world parity. And the jokes practically write themselves: TypeScript that lifts with .NET? Devs will either flex or flinch. For now, the curtain rises on a new contender, and the audience is leaning in.
Key Points
- •@tsonic/express provides Express-style HTTP server APIs for Tsonic, enabling TypeScript apps compiled to native binaries.
- •The setup requires the .NET 10 SDK, and ASP.NET Core dependencies are installed during initialization.
- •A quick start shows creating a project with npx tsonic, adding @tsonic/express, and defining a minimal App.ts route.
- •The API surface includes routing (GET/POST/PUT/DELETE/PATCH/ALL), middleware, error handlers, request/response helpers, body parsers, static files, and server lifecycle control.
- •Documentation covers advanced patterns and known compatibility gaps; the package follows runtime-major versioning (e.g., 10.x) and uses the MIT license.