Les faits techniques et les notes de mesure sont conservés en anglais afin d’éviter toute divergence entre les traductions.

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.

Commencer

Installez Perry et commencez à compiler TypeScript en exécutables natifs

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.

2Utilisation

Verify the toolchain

perry doctor

Checks the compiler, linker, SDK, and target setup

Compiler un fichier

perry compile main.ts

Compile main.ts en un exécutable natif

Sortie personnalisée

perry compile main.ts -o myapp

Spécifier le nom de l'exécutable de sortie

Avec le runtime V8

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

Activer V8 pour la compatibilité des paquets npm JavaScript

Vérifier la compatibilité

perry check ./src

Valider le code TypeScript pour la compilation 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.

Get Started with Perry

Commencer

1Installation

2Utilisation

Your first binary, step by step

Where to go next

Documentation

Showcase

Compare

GitHub