Os dados técnicos e as notas de medição são mantidos em inglês para evitar divergências entre traduções.

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.

Começar

Instale Perry e comece a compilar TypeScript para executáveis nativos

1Instalação

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 um arquivo

perry compile main.ts

Compila main.ts para um executável nativo

Saída personalizada

perry compile main.ts -o myapp

Especificar o nome do executável de saída

Com runtime V8

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

Ativar V8 para compatibilidade com pacotes npm JavaScript

Verificar compatibilidade

perry check ./src

Validar código TypeScript para compilação 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.

Get Started with Perry

Começar

1Instalação

2Uso

Your first binary, step by step

Where to go next

Documentation

Showcase

Compare

GitHub