A native module that re-exports an island package's names (`export { Type,
Static } from "typebox"`, pi's ai/src/index.ts) was refused with SC8010: the
re-export arm of the island import collection reported every export
declaration from an island package as a boundary, so an island value in
pi-ai's public API had no way to be written.
The barrel is now a module like any other: it loads the island package at
its own %init position (nodeIsland.defer, exactly as an import does),
snapshots the CommonJS named exports it re-exports, and registers each
re-exported name against the island's own export symbol. A name imported
from the barrel reaches that symbol through the checker's alias chain
(islandReexportOf), so islandBindingOf binds it as the island value it is —
including through a second barrel (`export { Num as NumberSchema } from
"./barrel.ts"`), since every re-exporting module registers the symbol its
chain ends on.
A namespace or star re-export has no name of its own to bind and stays
refused — and now actually reaches that refusal: the npm-import collection
skipped a star or namespace re-export before the island arm ran, so the
statement was silently dropped instead of refused. The guard routes it to
the island boundary refusal (a type-only star re-export stays erased like a
type-only named one), and the path-mapped re-export case in
node-island.test.ts pins that refusal with a star re-export rather than the
named one this commit makes work.
Test: tests/corpus/6898-node-island-reexport (a two-step barrel,
differential to Node, plain and sanitized).
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.