I dati tecnici e le note di misurazione sono mantenuti in inglese per evitare discrepanze tra le traduzioni.

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.

Inizia

Installa Perry e inizia a compilare TypeScript in eseguibili nativi

1Installazione

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.

2Utilizzo

Verify the toolchain
perry doctor

Checks the compiler, linker, SDK, and target setup

Compila un file
perry compile main.ts

Compila main.ts in un eseguibile nativo

Output personalizzato
perry compile main.ts -o myapp

Specifica il nome dell'eseguibile di output

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

Abilita V8 per la compatibilità con i pacchetti npm JavaScript

Verifica compatibilità
perry check ./src

Valida il codice TypeScript per la compilazione nativa

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