AOT TypeScript via SWC + LLVM — native builds with no external JavaScript engine

I dati tecnici e le note di misurazione sono mantenuti in inglese per evitare discrepanze tra le traduzioni.

Compila TypeScript in codice nativo.
One Codebase, Many Targets.

Perry compiles TypeScript to native GUI and CLI apps for macOS, iOS, iPadOS, visionOS, tvOS, watchOS, Android, Wear OS, Windows, Linux, and Web/WebAssembly, with a separate HarmonyOS preview. Native binaries statically link the Perry runtime and GC; they do not require Node.js or an external JavaScript engine.

Inizia Vedi su GitHub

terminal

$ perry compile main.ts

Compilazione di main.ts...

✓ Example executable written: main (size varies by linked features)

$ ./main

Hello, World!

11 + preview

Documented targets + preview

35+

Widget UI nativi

~3.2 ms

Measured runtime-only macOS hello

Store workflows

perry publish

In produzione

App reali, compilate da TypeScript con Perry.

Vedi tutti i progetti

Mango

Native MongoDB GUI. ~7 MB binary, <1s cold start.

Hone

Native code editor with built-in terminal, Git, LSP, sync.

dB Meter

Real-time decibel meter with 60 fps live waveform.

{ }

Pry

Fast native JSON viewer — tree, search, keyboard shortcuts.

Perché Perry?

The current compiler, runtime, UI, and tooling surfaces — with limitations called out

No External JS Engine

Native builds run without Node.js, Bun, Deno, or an external JavaScript engine installed. The Perry runtime and garbage collector are statically linked into each target-specific binary.

Compilazione veloce

Compilazione diretta da TypeScript a codice nativo usando SWC per il parsing e LLVM per la generazione del codice ottimizzato. Nessun JavaScript intermedio.

Size Scales With Features

Hello world can be about 330 KB and Mango is published at about 7 MB. Applications that link the full standard library or optional V8 fallback can be much larger; size depends on target, imports, and build profile.

Cacheable Builds

Perry caches module objects and can pin a CPU baseline for portable output. Default host builds tune for the local CPU, and final binaries may contain platform UUIDs, timestamps, or signatures, so byte-for-byte cross-machine reproducibility is not promised.

Tracked Node.js APIs

Native implementations cover many familiar Node.js APIs across 53 tracked modules. Coverage is broad but not complete; use perry check and the published limitations for your project.

Veri pacchetti npm

Many pure TypeScript and JavaScript packages compile natively. Packages that depend on unsupported dynamic or engine-specific semantics may need the optional embedded V8 fallback or may not work.

35+ Native UI Widgets

35+ native UI widgets map to platform toolkits including AppKit, UIKit, GTK4, Win32, Android SDK APIs, SwiftUI on watches, and a DOM/CSS bridge on Web/WASM. Availability varies by target.

Compile-Time Plugin System

Modules can compose at build time and statically linked dependencies can become direct native calls. Dynamic dispatch and runtime support remain where JavaScript semantics require them.

True Multi-Threading

Real OS threads with parallelMap, parallelFilter, and spawn. Mutable captures are rejected by default; SharedArrayBuffer and Atomics provide explicit shared-memory coordination, with documented typed-view caveats.

Compile-Time i18n

Automatic string extraction, CLDR plural rules for 30+ locales, and compile-time validation. Translations are baked into the binary; lookup cost depends on the generated catalog and call site.

Approfondisci: come Perry compila TypeScript in un binario, cosa lo rende un compilatore nativo per TypeScript e come si confronta con le alternative a Electron.

Guarda cosa le persone costruiscono

Public native applications compiled from TypeScript, with platforms and capabilities taken from their current project pages.

Mango

GUI MongoDB nativa — costruita interamente in TypeScript

macOSLinuxWindows

Hone

Editor di codice nativo con IA — da TypeScript a binario nativo

macOSiOSWeb

Vedi tutti i progetti

Native across documented targets

Eleven documented targets share Perry’s compiler and UI model. Web and WASM are aliases; visionOS, watchOS, and Wear OS have narrower core support, and HarmonyOS is a separate preview.

macOS

AppKit

Broad support

iOS

UIKit

Broad support

iPadOS

UIKit

Broad support

visionOS

UIKit (2D)

Core support

tvOS

UIKit

Broad support

watchOS

SwiftUI

Core support

Android

Android SDK

Broad support

Wear OS

Android SDK

Core support

Windows

Win32

Broad support

Linux

GTK4

Broad support

Web / WASM

DOM/CSS bridge

Broad support

--target web and --target wasm are aliases

HarmonyOS

ArkUI

Preview

Separate preview; not included in the 11 documented targets

11 documented targets; HarmonyOS is listed separately as a preview. See the platform status guide

Dal codice all’App Store

The perry publish command supports build, signing, packaging, verification, and submission workflows. Availability and prerequisites vary by platform and hosted-service configuration.

perry compileCompila e firma

perry publishImpacchetta e invia

Store e downloadApp Store, Play Store, diretto

perry verifyVerify supported targets

perry compileCompila e firma

perry publishImpacchetta e invia

Store e downloadApp Store, Play Store, diretto

perry verifyVerify supported targets

Build & Sign

Create platform artifacts and use configured signing credentials. Apple, Android, and Windows workflows require their platform SDKs, accounts, and certificates.

Distribute

Prepare store submissions or direct-download artifacts for supported targets. Store acceptance and processing remain controlled by each store.

Verify

Run available launch and UI checks through Perry and Geisterhand. Test depth and target coverage depend on the selected environment.

Local compilation is free and MIT licensed. Check hosted-service availability → /publish

Confronto framework

Perry’s native compilation model

Ahead-of-time machine code and real platform widgets, with an explicitly linked runtime and documented compatibility tradeoffs.

Designed for

✓Ahead-of-time machine code through LLVM
✓Real platform widgets where each target supports them
✓No external Node.js installation or JavaScript engine by default

Tradeoffs to evaluate

–The Perry runtime and GC are statically linked; overhead is not “none”
–Perry implements a practical TypeScript and Node.js subset; some packages need the optional V8 fallback
–Platform capabilities and maturity differ across desktop, mobile, wearable, TV, and Web/WASM targets

Competitor-specific pages are dated and link to upstream documentation. View sourced comparisons

Scrivi TypeScript, distribuisci nativo

Use familiar TypeScript syntax and validate each API or package against Perry’s current compatibility surface.

hello.ts

// hello.ts
const greeting = "Hello, World!";
console.log(greeting);
 
// Output size varies with target and linked features
// No external JavaScript runtime installation needed!

$ perry compile hello.ts

Binario nativo

Published measurements

Current public results include wins, mixed results, and losses. Treat microbenchmarks as workload-specific measurements, not a universal speed claim.

Metrica	Perry	Node.js	Bun
Dimensione binario	~330 KB hello world; ~7 MB Mango	Application plus an installed Node.js runtime	Standalone executable embeds the Bun runtime
Tempo di avvio	~3.2 ms*	Engine boot and warmup; workload-dependent	Engine boot and warmup; workload-dependent
Dipendenze runtime	Statically linked Perry runtime + GC	External Node.js runtime	Embedded Bun / JavaScriptCore runtime
Overhead memoria	Workload-dependent	Workload-dependent	Workload-dependent

* Measured runtime-only macOS hello world on an Apple M-series host (5.0 → 3.2 ms after removing unused dynamic-library links). Application startup varies.

Full public suite: wins and losses

Perry 0.5.1355 · Node.js 22.23.1 · Bun 1.3.14 · Apple M1, 8 GB · 2026-08-08

Lower wall-clock median is better. Five complete process samples; correctness checks passed. Benchmark names and descriptions remain English technical identifiers.

Benchmark	Perry	Node.js	Bun	Result
factorial Modular accumulation	94 ms	95 ms	95 ms	Win vs both
method calls Class method dispatch	9 ms	10 ms	8 ms	Mixed
closure Closure creation and invocation	47 ms	49 ms	49 ms	Win vs both
binary trees Tree allocation and traversal	4 ms	6 ms	6 ms	Win vs both
string concat String append loop	2 ms	4 ms	1 ms	Mixed
prime sieve Sieve of Eratosthenes	28 ms	6 ms	5 ms	Loss vs both
mandelbrot Complex-number iteration	22 ms	24 ms	28 ms	Win vs both
matrix multiply Matrix multiplication	85 ms	33 ms	33 ms	Loss vs both
JSON roundtrip Parse and stringify ~1 MB JSON	184 ms	380 ms	220 ms	Win vs both

Raw benchmark artifact Methodology and caveats

Inizia

Installa Perry e inizia a compilare TypeScript in eseguibili nativi

1Installazione

terminal

$ npm install -g @perryts/perry

Recommended cross-platform install. Native targets still require the relevant platform SDK and linker; run perry doctor after installation.

2Utilizzo

Verify the toolchain

perry doctor

Checks the compiler, linker, SDK, and target setup

Compila un file

perry compile main.ts

Compila main.ts in un eseguibile nativo

Output personalizzato

perry compile main.ts -o myapp

Specifica il nome dell'eseguibile di output

Con runtime V8

perry compile main.ts --enable-js-runtime

Abilita V8 per la compatibilità con i pacchetti npm JavaScript

Verifica compatibilità

perry check ./src

Valida il codice TypeScript per la compilazione nativa

Supporto delle funzionalità

Tested surfaces and known partial areas — not a blanket claim of complete TypeScript or Node.js compatibility

Linguaggio base

✓Numbers (f64 + selected unboxed representations)
✓Strings (UTF-8)
✓Booleans
✓Arrays
✓Objects
✓BigInt (fixed 1024-bit)
–Proxy
–eval / runtime-generated code

Funzioni

✓Function declarations
✓Arrow functions
✓Default parameters
✓Rest parameters
✓Closures
✓Higher-order functions
✓Async / await
–Runtime-computed dynamic import

Classi

✓Classes and constructors
✓Private fields (#)
✓Static methods / fields
✓Getters / setters
✓Inheritance and super
–Decorators and reflection
–Dynamic prototype manipulation
–Weak references / finalizers

Sistema di tipi

✓Type annotations
✓Local type inference
✓Generics / specialization
✓Interfaces
✓Union types and guards
–Runtime type validation

Libreria standard

–fs / path / os
–crypto
–Buffer and streams
–http / http2 / net / tls
–child_process / worker_threads
–WebAssembly global
–~97% Node suite · 53 modules

✓Tested in the current implementation–Partial

“Partial” means the API or syntax exists with documented gaps. Exact behavior changes as parity work lands. Read the current limitations

~50 Native Packages and Node APIs

Many popular packages and Node APIs have native implementations. Coverage is package- and feature-specific; perry check and the compatibility documentation are the source of truth.

Database

mysql2pgmongodbbetter-sqlite3ioredis

Sicurezza

bcryptargon2jsonwebtokencrypto

HTTP

httphttpsaxiosnode-fetchwsnodemailer

Elaborazione dati

cheeriosharpzliblodash

Data e ora

dayjsmomentdate-fnsnode-cron

Utilità

uuidnanoidslugifyvalidatordotenvrate-limiter-flexible

Import the package normally. Perry selects a native implementation when one is available, otherwise compilation may use another supported path or report a limitation.

Come funziona

From TypeScript source through SWC, Perry HIR, LLVM, and the linked runtime

TypeScriptFile .ts

SWC

ParserParsing veloce

HIR

TrasformazioneMonomorphization

LLVM

CodegenCodice macchina

EseguibileFrom ~330 KB; varies by features

Vuoi sapere come funziona il compilatore sotto il cofano? Meccanismi interni del compilatore

Approfondimento: TypeScript su LLVM — monomorfizzazione, NaN-boxing e perché Perry ha abbandonato Cranelift.

Progetto adiacente a Perry · Pre-1.0

Un posto dove il codice Perry può riposare ed essere eseguito.

Coop trasforma una directory di TypeScript compatibile con Perry in una libreria applicativa nativa e la serve via HTTP, fornendo runtime e libreria standard di Perry una sola volta per macchina.

✓Runtime provider condivisi
✓Un worker per deployment
✓Distribuisci, ispeziona e ripristina

Scopri Coop Vedi il sorgente

TypeScript

Perry

Libreria applicativa

Worker Coop

Runtime + libreria standard condivisiuno per macchina

Domande frequenti

Tutto quello che si chiede prima di compilare il primo binario

Perry ha bisogno di Node.js o di un runtime?

Native Perry binaries run without Node.js, Bun, Deno, or an external JavaScript engine installed. They do include the Perry runtime and garbage collector, statically linked. Packages that need engine semantics can use the optional embedded V8 fallback.

Quanto sono grandi i binari compilati?

Size depends on the target, imports, and build profile. The published examples range from about 330 KB for hello world to about 7 MB for Mango; full-standard-library or optional-V8 builds can be much larger. Treat any size as a measured example, not a universal output size.

Posso usare i pacchetti npm?

Many pure TypeScript/JavaScript packages compile natively, and roughly 50 package/API implementations are tracked. Compatibility is not universal: packages using native addons, unsupported dynamic behavior, or engine-specific semantics may need the optional V8 fallback or may not work. Run perry check and consult the limitations.

Quali piattaforme supporta Perry?

Perry documents 11 targets: macOS, iOS, iPadOS, visionOS, tvOS, watchOS, Android, Wear OS, Windows, Linux, and Web/WASM. Web and WASM are aliases; HarmonyOS is a separate preview. Platform maturity and API coverage differ, so consult the platform guide.

Perry è gratuito e open source?

The compiler and runtime repository is MIT licensed, and local compilation requires no account. Hosted Perry Publish and commercial support are separate services; availability, limits, and pricing are confirmed in the service or in writing.

In cosa Perry è diverso da Bun o da deno compile?

Bun and Deno standalone executables bundle their runtimes; Perry native builds compile through LLVM and do not embed a JavaScript engine by default, although they statically link the Perry runtime and GC. Exact size and startup comparisons are version-, platform-, and workload-specific. See the dated Perry vs Bun and Perry vs Deno pages.

In cosa Perry è diverso da Electron o Tauri?

Electron ships Chromium and Node.js; Tauri uses a system webview with native-side application code. Perry instead maps its UI model to platform widgets where supported. Bundle size and platform capability vary, so use the dated Perry vs Electron and Perry vs Tauri comparisons rather than a universal size claim.

Quanto è maturo Perry?

Perry is pre-1.0 and changes quickly. Real projects use it today, but language, package, and platform parity are still active work. Review the showcase, current limitations, and changelog before committing a production workload.

Altre domande? Leggi la guida introduttiva o chiedi su GitHub Discussions.

Compila TypeScript in codice nativo.One Codebase, Many Targets.

Perché Perry?

No External JS Engine

Compilazione veloce

Size Scales With Features

Cacheable Builds

Tracked Node.js APIs

Veri pacchetti npm

35+ Native UI Widgets

Compile-Time Plugin System

True Multi-Threading

Compile-Time i18n

Guarda cosa le persone costruiscono

Mango

Hone

Native across documented targets

macOS

iOS

iPadOS

visionOS

tvOS

watchOS

Android

Wear OS

Windows

Linux

Web / WASM

HarmonyOS

Dal codice all’App Store

Build & Sign

Distribute

Verify

Perry’s native compilation model

Designed for

Tradeoffs to evaluate

Scrivi TypeScript, distribuisci nativo

Published measurements

Full public suite: wins and losses

Inizia

1Installazione

2Utilizzo

Supporto delle funzionalità

Linguaggio base

Funzioni

Classi

Sistema di tipi

Libreria standard

~50 Native Packages and Node APIs

Database

Sicurezza

HTTP

Elaborazione dati

Data e ora

Utilità

Come funziona

Un posto dove il codice Perry può riposare ed essere eseguito.

Domande frequenti

Perry ha bisogno di Node.js o di un runtime?

Quanto sono grandi i binari compilati?

Posso usare i pacchetti npm?

Quali piattaforme supporta Perry?

Perry è gratuito e open source?

In cosa Perry è diverso da Bun o da deno compile?

In cosa Perry è diverso da Electron o Tauri?

Quanto è maturo Perry?

Compila TypeScript in codice nativo.
One Codebase, Many Targets.