Three shapes from pi's process/child helpers: 1. A cleanup arrow such as `() => process.off(signal, handler)` sits in @types/node's `Process`-returning slot. The lambda's ABI was decided from its inferred return type before the contextual void slot was consulted, so the arrow promised a `Process` value the lowering cannot produce and the registration fenced. `lambdaSignature` now takes the contextual void answer first; the adoption block further down already computes it, so every program that compiles today keeps its IR. 2. `child.off`/`removeListener` were unimplemented. They join the `child.on` family, are limited to the removable literals `spawn`, `exit`, `close` and `error`, and require the listener value that was registered — removal is by closure identity, scanning the registry from the end as Node does. New C runtime entry points `scr_child_off_spawn/_exit/_close/_error` release the entry and shift the tail. 3. `child.signalCode` reads `string | null` from the recorded exit signal, with `scr_child_has_signal_code`/`scr_child_signal_code` behind the same typed-union wrap as `spawnRes.signal`; the IR validator pins the `string | null` result. The process listener registration paths (stdin events, IPC message and disconnect, uncaughtException and uncaughtExceptionMonitor, unhandledRejection, warning, signals, exit) now accept any discarded expression, matching `child.on` — `resultIsDiscarded` rather than a bare expression statement — so `handlers.push(() => process.off(…))` compiles. Evidence: corpus 8412 (removal through `off` and `removeListener` for all four events, `signalCode` while running, after a normal exit, after a fatal signal and after a failed spawn, idempotent double removal) and the `node-types` fixture plus project-config test that pins pi's exact `() => process.off(...)` cleanup closure. Ambient declarations gain the `signalCode` property and the four `off`/`removeListener` overloads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scriptc
scriptc compiles TypeScript and JavaScript to native executables and WebAssembly. It uses the types checked by the TypeScript compiler to generate machine code, and the output runs without Node.js installed. npm packages your program imports compile along with it. Code scriptc can't compile is reported at build time with a diagnostic and, where available, a rewrite hint.
scriptc is experimental and supports a subset of JavaScript, TypeScript, and Node.js APIs. Run scriptc coverage on an existing program to see how much of it compiles, and see the limitations and Node.js compatibility reference for details.
Installation
Install with Node.js 24 or later and npm:
$ npm install -g scriptc
The installed compiler runs natively on macOS, Linux, and Windows. Node.js is needed only to install it and to run WASI modules with scriptc run. Standalone compiler archives are also available from GitHub Releases.
Building executables requires a linker and the platform SDK or sysroot. See the quickstart for prerequisites and platform support for host requirements, cross-compilation, and WebAssembly.
Build a program
Create hello.ts:
const who = process.argv.length > 2 ? process.argv[2] : "world";
console.log(`hello, ${who}`);
scriptc run compiles the file and runs the result:
$ scriptc run hello.ts
hello, world
scriptc build writes an executable:
$ scriptc build hello.ts -o hello >/dev/null
$ ./hello scriptc
hello, scriptc
These examples use POSIX shell syntax. On Windows, build hello.exe and run it with .\hello.exe.
Use scriptc coverage hello.ts to check what compiles before you build. See coverage reports for details.
Use Node APIs
Supported Node APIs compile to the native runtime. For example, server.ts:
import { createServer } from "node:http";
const server = createServer((req, res) => {
res.setHeader("content-type", "application/json");
res.end(JSON.stringify({ path: req.url }));
});
server.listen(8080, () => {
console.log("listening on http://localhost:8080");
});
$ scriptc build server.ts -o server >/dev/null
$ ./server
listening on http://localhost:8080
Use npm packages
npm packages compile into the executable with your code, so it doesn't read node_modules at runtime.
Create cli.ts:
import pc from "picocolors";
console.log(pc.green("hello from scriptc"));
$ npm install picocolors
$ scriptc build cli.ts -o cli >/dev/null
$ ./cli
hello from scriptc
Package support is partial. See npm dependencies for which packages compile and how to check them.
Documentation
- Introduction: what scriptc is and what you can build.
- Quickstart: installation and your first executable.
- Coverage reports: check whether an existing program compiles.
- Platform support: cross-compilation and WebAssembly.
- CLI reference: commands, options, and output formats.
- Native program objects: use compiler output in external builds.
- Native FFI: call C ABI functions from compiled programs.
- WebAssembly modules: build and embed WASI modules.
- Examples: programs and integration examples in this repository.
Contributing
See CONTRIBUTING.md for source setup, testing, native artifact builds, and docs development.