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

Fakta teknis dan catatan pengukuran dipelihara dalam bahasa Inggris untuk mencegah perbedaan antar-terjemahan.

Kompilasi TypeScript ke Native.
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.

Mulai Lihat di GitHub

terminal

$ perry compile main.ts

Mengompilasi main.ts...

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

$ ./main

Hello, World!

11 + preview

Documented targets + preview

35+

Widget UI native

~3.2 ms

Measured runtime-only macOS hello

Store workflows

perry publish

Berjalan di produksi

Aplikasi nyata, dikompilasi dari TypeScript dengan Perry.

Lihat semua proyek showcase

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.

Mengapa 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.

Kompilasi Cepat

Kompilasi langsung dari TypeScript ke kode native menggunakan SWC untuk parsing dan LLVM untuk pembuatan kode yang dioptimalkan. Tanpa JavaScript perantara.

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.

Paket npm Nyata

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.

Pelajari lebih dalam: bagaimana Perry mengompilasi TypeScript menjadi binary, apa yang membuatnya menjadi kompiler TypeScript native, dan bagaimana perbandingannya dengan alternatif Electron.

Lihat Apa yang Orang Bangun

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

Mango

GUI MongoDB native — dibangun sepenuhnya dengan TypeScript

macOSLinuxWindows

Hone

Editor kode native bertenaga AI — TypeScript ke binary native

macOSiOSWeb

Lihat semua proyek showcase

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

Dari Kode ke 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 compileKompilasi & tanda tangani

perry publishKemas & kirim

Toko & UnduhanApp Store, Play Store, langsung

perry verifyVerify supported targets

perry compileKompilasi & tanda tangani

perry publishKemas & kirim

Toko & UnduhanApp Store, Play Store, langsung

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

Perbandingan 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

Tulis TypeScript, Kirim Native

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

Binary native

Published measurements

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

Metrik	Perry	Node.js	Bun
Ukuran Binary	~330 KB hello world; ~7 MB Mango	Application plus an installed Node.js runtime	Standalone executable embeds the Bun runtime
Waktu Mulai	~3.2 ms*	Engine boot and warmup; workload-dependent	Engine boot and warmup; workload-dependent
Dependensi Runtime	Statically linked Perry runtime + GC	External Node.js runtime	Embedded Bun / JavaScriptCore runtime
Overhead Memori	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

Mulai

Instal Perry dan mulai mengompilasi TypeScript menjadi executable native

1Instalasi

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.

2Penggunaan

Verify the toolchain

perry doctor

Checks the compiler, linker, SDK, and target setup

Kompilasi file

perry compile main.ts

Mengompilasi main.ts menjadi executable native

Output kustom

perry compile main.ts -o myapp

Tentukan nama executable output

Dengan runtime V8

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

Aktifkan V8 untuk kompatibilitas paket npm JavaScript

Periksa kompatibilitas

perry check ./src

Validasi kode TypeScript untuk kompilasi native

Dukungan Fitur

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

Bahasa Inti

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

Fungsi

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

Kelas

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

Sistem Tipe

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

Standard Library

–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

Keamanan

bcryptargon2jsonwebtokencrypto

HTTP

httphttpsaxiosnode-fetchwsnodemailer

Pemrosesan Data

cheeriosharpzliblodash

Tanggal & Waktu

dayjsmomentdate-fnsnode-cron

Utilitas

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.

Cara Kerjanya

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

TypeScriptFile .ts

SWC

ParserParsing cepat

HIR

TransformasiMonomorphization

LLVM

CodegenKode mesin

ExecutableFrom ~330 KB; varies by features

Ingin tahu bagaimana kompiler bekerja di balik layar? Struktur internal kompiler

Pendalaman: TypeScript di atas LLVM — monomorphization, NaN-boxing, dan mengapa Perry meninggalkan Cranelift.

Proyek yang berdekatan dengan Perry · Pre-1.0

Tempat kode Perry beristirahat dan berjalan.

Coop mengubah direktori TypeScript yang kompatibel dengan Perry menjadi pustaka aplikasi native dan menyajikannya lewat HTTP, sementara runtime dan pustaka standar Perry disediakan sekali per mesin.

✓Runtime bersama
✓Satu worker per deployment
✓Deploy, periksa, dan rollback

Jelajahi Coop Lihat sumber

TypeScript

Perry

Pustaka aplikasi

Worker Coop

Runtime + pustaka standar bersamasatu per mesin

Pertanyaan yang Sering Diajukan

Semua yang ditanyakan orang-orang sebelum mengompilasi binary pertama mereka

Apakah Perry membutuhkan Node.js atau 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.

Seberapa besar binary yang dikompilasi?

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.

Bisakah saya menggunakan paket 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.

Platform apa saja yang didukung 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.

Apakah Perry gratis dan 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.

Apa bedanya Perry dengan Bun atau 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.

Apa bedanya Perry dengan Electron atau 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.

Seberapa matang 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.

Ada pertanyaan lain? Baca panduan memulai atau tanyakan di GitHub Discussions.

Kompilasi TypeScript ke Native.One Codebase, Many Targets.

Mengapa Perry?

No External JS Engine

Kompilasi Cepat

Size Scales With Features

Cacheable Builds

Tracked Node.js APIs

Paket npm Nyata

35+ Native UI Widgets

Compile-Time Plugin System

True Multi-Threading

Compile-Time i18n

Lihat Apa yang Orang Bangun

Mango

Hone

Native across documented targets

macOS

iOS

iPadOS

visionOS

tvOS

watchOS

Android

Wear OS

Windows

Linux

Web / WASM

HarmonyOS

Dari Kode ke App Store

Build & Sign

Distribute

Verify

Perry’s native compilation model

Designed for

Tradeoffs to evaluate

Tulis TypeScript, Kirim Native

Published measurements

Full public suite: wins and losses

Mulai

1Instalasi

2Penggunaan

Dukungan Fitur

Bahasa Inti

Fungsi

Kelas

Sistem Tipe

Standard Library

~50 Native Packages and Node APIs

Database

Keamanan

HTTP

Pemrosesan Data

Tanggal & Waktu

Utilitas

Cara Kerjanya

Tempat kode Perry beristirahat dan berjalan.

Pertanyaan yang Sering Diajukan

Apakah Perry membutuhkan Node.js atau runtime?

Seberapa besar binary yang dikompilasi?

Bisakah saya menggunakan paket npm?

Platform apa saja yang didukung Perry?

Apakah Perry gratis dan open source?

Apa bedanya Perry dengan Bun atau Deno compile?

Apa bedanya Perry dengan Electron atau Tauri?

Seberapa matang Perry?

Kompilasi TypeScript ke Native.
One Codebase, Many Targets.