Các dữ kiện kỹ thuật và ghi chú đo lường được duy trì bằng tiếng Anh để tránh sai lệch giữa các bản dịch.
Get Started with Perry
From zero to a running native executable in three steps. Native output does not need Node.js or an external JavaScript engine on the target machine; Perry's runtime and GC are linked into it.
Bắt đầu
Cài đặt Perry và bắt đầu biên dịch TypeScript thành tệp thực thi gốc
1Cài đặt
$ npm install -g @perryts/perryRecommended cross-platform install. Native targets still require the relevant platform SDK and linker; run perry doctor after installation.
2Sử dụng
perry doctorChecks the compiler, linker, SDK, and target setup
perry compile main.tsBiên dịch main.ts thành tệp thực thi gốc
perry compile main.ts -o myappChỉ định tên tệp thực thi đầu ra
perry compile main.ts --enable-js-runtimeBật V8 để tương thích với các gói npm JavaScript
perry check ./srcXác thực mã TypeScript cho biên dịch gốc
Your first binary, step by step
Once Perry is installed, compiling TypeScript to a native executable is a single command. Write a file:
const name = process.argv[2] ?? "World";
console.log(`Hello, ${name}!`);Compile it and run the result — the output is a self-contained machine-code binary, not a bundled script:
$ perry compile hello.ts
✓ Compiled executable: hello
$ ./hello Perry
Hello, Perry!
The published runtime-only hello-world measurement is about 3.2 ms on the documented Apple M-series test host. Real startup depends on the target, linked features, I/O, and hardware. Read more about how Perry compiles TypeScript to a binary or what happens inside the TypeScript native compiler.
Where to go next
Documentation
Guides for the CLI, Perry UI widgets, threading, i18n, platform prerequisites, and known limitations.
Showcase
Public applications and examples built with Perry, with measurements labeled where evidence is available.
Compare
How Perry stacks up against Bun, Deno, Electron, Tauri, React Native, and Static Hermes.
GitHub
Source, issues, and discussions — Perry is open source.