The pack builds the ICU archive with the same Zig C++ recipe, adds scr_intl.c as an optional unit under the intl predicate, and publishes the archive under the id "icu". Its data file (icudt78l.dat) is not a link input: the pack lists it in a new manifest "data" array, and every Intl build copies it next to the executable it links (verifyArtifact checked, atomic copy, size-checked before reuse). A pack that omits scr_intl.c refuses an Intl program with SC3002 instead of linking undefined scr_intl_ references. The pack fetches both ICU inputs from the pinned release assets: the source tarball (verified, cached, unpacked by the system tar) for the archive, and the data zip (sha256 and size pinned twice) for the data, unpacked by a small stored/deflate reader. Nothing is embedded in a binary. The runtime fingerprint keeps covering the vendored trees, the pinned ICU version keys the archive path, and the pack matrix gains the icu archive with the intl predicate. The isolated native host (native/compiler.ts) links outside the in-process linker and writes its executables synchronously, so it installs the same data artifacts itself (installNativeRuntimeData); the stored pack selection gains a schema version so a selection cached before the data list existed is discarded rather than trusted. Nothing selects a data artifact for a program without the intl feature. The sanitized lane links the pack's ICU archive as shipped. ICU is C++ and compiles with Zig's C++ driver for the packs' glibc floor, so it cannot ride the sanitizer lane's per-TU C rebuild, and instrumenting ~600 C++ TUs would add a multi-minute build to the first Intl program in every sanitized lane. scr_intl.c itself still compiles instrumented with every other runtime unit, and AddressSanitizer's interceptors cover ICU's allocations. 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.