JavaScript leaves the engine behind.

Porffor turns JavaScript and TypeScript into native executables ahead of time. These docs explain where that works, where it bends, and how to get useful results today.

Choose your route

You do not need to read this manual front to back. Start with the outcome you want.

Run one fileInstall Porffor and execute your first program. Ship a binaryKeep the executable, tune it, and move it. Serve HTTPCompile a fetch-style handler into a server. Adapt a projectBundle imports and audit runtime assumptions.

Install the tool

The installer places a single executable named porf in ~/.local/bin. Run it again later to update.

terminal

$ curl -fsSL https://porffor.dev/install.sh | sh
$ porf --version

A system C compiler gives the best results. On macOS, install Command Line Tools. On Debian or Ubuntu, install build-essential. If that is not possible, Porffor includes TCC and can use it with --compiler=tcc.

Platform note

Windows is currently a WSL workflow. Native Windows output is not part of the supported path yet.

Know what you are holding

Source goes in

Porffor parses JavaScript or TypeScript itself. Type syntax needs no separate transform.

A native program comes out

The final artifact is an ordinary executable for the OS and architecture that built it.

No JavaScript engine ships with it

The language runtime and only the built-ins your program needs are compiled into the artifact.

Expectation

Porffor is pre-alpha. Treat compatibility as something to verify, not something to assume. The runtime surface page is the contract for today.