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

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.

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

Your first binary, step by step

Once Perry is installed, compiling TypeScript to a native executable is a single command. Write a file:

hello.ts
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:

terminal

$ 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