Technische Fakten und Messhinweise werden zur Vermeidung von Abweichungen in englischer Sprache gepflegt.

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.

Loslegen

Installiere Perry und beginne TypeScript zu nativen Binaries zu kompilieren

1Installation

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.

2Verwendung

Verify the toolchain
perry doctor

Checks the compiler, linker, SDK, and target setup

Datei kompilieren
perry compile main.ts

Kompiliert main.ts zu einem nativen Binary

Benutzerdefinierte Ausgabe
perry compile main.ts -o myapp

Name der Ausgabedatei angeben

Mit V8-Laufzeitumgebung
perry compile main.ts --enable-js-runtime

V8 für JavaScript-npm-Paket-Kompatibilität aktivieren

Kompatibilität prüfen
perry check ./src

TypeScript-Code für native Kompilierung validieren

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