Los datos técnicos y las notas de medición se mantienen en inglés para evitar divergencias entre traducciones.

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.

Comenzar

Instala Perry y empieza a compilar TypeScript a ejecutables nativos

1Instalación

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.

2Uso

Verify the toolchain
perry doctor

Checks the compiler, linker, SDK, and target setup

Compilar un archivo
perry compile main.ts

Compila main.ts a un ejecutable nativo

Salida personalizada
perry compile main.ts -o myapp

Especificar el nombre del ejecutable de salida

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

Habilitar V8 para compatibilidad con paquetes npm de JavaScript

Verificar compatibilidad
perry check ./src

Validar código TypeScript para compilación 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