SharpTS
Run TypeScript Natively on .NET via AOT Compilation
Details
- External ID
- 46557698
- Source
- HN
- Company
- —
- Product
- SharpTS
- Website domain
- github.com
- Launched
- Jan. 9, 2026
- Cohort
- —
- Upvotes
- 6
- Upvotes percentile
- 0.2549407114624506
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:25 p.m.
- Updated at
- Sept. 7, 2026, 9:25 p.m.
Description
Hey HN! I'm the author of SharpTS, a TypeScript interpreter and ahead-of-time compiler written in C#.*What makes it different:*- Dual execution modes - interpret TypeScript directly OR compile to native .NET executables - Full C# interop - compile TypeScript to DLLs that C# projects can reference with full type safety*What works today:*- Core TypeScript: classes, interfaces, generics, async/await, decorators - Advanced types: union/intersection types, literal types, type guards - Compiles to verifiable .NET IL with performance comparable to hand-written C# - 80+ unit tests, supports most of TypeScript's feature set*Why I built it:*I wanted to understand how TypeScript really works under the hood, and I thought .NET developers might appreciate being able to run TypeScript without Node.js. The AOT compilation to .NET IL was a fun challenge - mapping TypeScript's structural type system to .NET's nominal types required some creative solutions.*Current limitations:*- No npm module support (yet) - Some advanced type system features are still in progress - Standard library is partial (see STATUS.md)The repo has detailed architecture docs if you're curious about the implementation details. Would love feedback, especially from TypeScript or compiler folks!Example usage: ``` # Install dotnet tool install -g SharpTS# Interpret sharpts script.ts# Compile to .NET sharpts --compile script.ts dotnet script.dll ```Happy to answer questions!
Enrichment
- Theme
- browser automation and scraping for AI
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- run typescript natively on .net
- Manually corrected
- False
Could you build this?
No Building an ahead-of-time compiler and native runtime interpreter for TypeScript in C# requires deep compiler engineering and language specification knowledge.
What it would actually take: Requires writing a full TypeScript AST parser, type checker, semantic analyzer, and IL code generator or native code emitter via .NET Roslyn or RyuJIT backend. TypeScript's complex structural typing system, dynamic JS semantics, and interop with the CLR type system represent immense compiler architecture challenges that vibe coding cannot handle.
Discussion
1 comment analyzed.
Feature requests: Support for older .NET versions
Competitors
Other products that read as similar to this one — 212 launches clear the similarity bar, closest 8 shown.
Attention rank: #176 of 213 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 69 days after the earliest competitor.
- Typical is TypeScript with type-safety at runtime · hn · 2026-01-11 · 8 upvotes · similarity 0.59
- TypeScript 6.0 · ph · 2026-03-24 · 156 upvotes · similarity 0.53
- Crust · hn · 2026-03-17 · 95 upvotes · similarity 0.52
- lucent · github · 2026-09-21 · 17 upvotes · similarity 0.51
- mcp-tada · github · 2026-09-10 · 23 upvotes · similarity 0.50
- CodeDrift · hn · 2026-03-05 · 5 upvotes · similarity 0.49
- I wrote a book · hn · 2025-12-08 · 53 upvotes · similarity 0.48
- Ironwall, a safety-first native programming language and compiler · hn · 2026-06-06 · 16 upvotes · similarity 0.48
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.