技術的な事実と測定上の注意事項は、翻訳間のずれを防ぐため英語を正本として管理しています。

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.

はじめる

Perryをインストールして、TypeScriptをネイティブ実行ファイルにコンパイルしましょう

1インストール

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.

2使い方

Verify the toolchain
perry doctor

Checks the compiler, linker, SDK, and target setup

ファイルをコンパイル
perry compile main.ts

main.tsをネイティブ実行ファイルにコンパイルします

カスタム出力
perry compile main.ts -o myapp

出力実行ファイル名を指定します

V8ランタイム付き
perry compile main.ts --enable-js-runtime

JavaScript npmパッケージの互換性のためにV8を有効化

互換性チェック
perry check ./src

TypeScriptコードのネイティブコンパイル互換性を検証します

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

Documentation

Guides for the CLI, Perry UI widgets, threading, i18n, platform prerequisites, and known limitations.

Showcase

Public applications and examples built with Perry, with measurements labeled where evidence is available.

Compare

How Perry stacks up against Bun, Deno, Electron, Tauri, React Native, and Static Hermes.

GitHub

Source, issues, and discussions — Perry is open source.