Chris Tate 6c3affab90 Read array-like elements for join, flat and flatMap in specification order
join checked each index with HasProperty before reading it, so a proxy's
has trap ran, and could hide a value or throw. flat converted its depth
only after it had read every index, and flatMap ran every callback before
it flattened any result, so a later read or callback could change an
array that should already have been copied.

- join reads every index with Get alone; a missing index joins as the
  empty string.
- flat converts its depth after the length and before the first index,
  and flatMap checks its callback there.
- Each present value, mapped first for flatMap, is flattened into the
  result before the next index is read, through the array dispatch's
  flat over `[value]`.

scr_dyn.h declares scr_dyn_array_like_call and scr_dyn_builtin_prototype,
the entry points of the two gated units, so every scr_* name the backend
can emit has a prototype in scr_runtime.h. The array-like corpus program's
logging proxy answers its has trap with `in` instead of Reflect.has, which
has no static lowering, so the program stays fully static.
2026-10-29 18:32:55 -05:00
2026-10-28 20:50:23 -05:00
…
…

scriptc

Vercel Labs Experiment npm version: scriptc License: Apache-2.0 npm downloads per month: 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

Contributing

See CONTRIBUTING.md for source setup, testing, native artifact builds, and docs development.

S
Description
GitHub Trending: vercel-labs/scriptc
Readme Apache-2.0
1 GiB
Languages
TypeScript 69.5%
C 21.3%
JavaScript 8.5%
C++ 0.7%