Malte UblandClaude Opus 5.5 ea9b70d1ad Cross island records of intersection types out as copies
An island export whose declared type is an INTERSECTION of record types —
typebox's `Type.Unsafe<{[K in "fg" | "bg"]: V} & {[K in "accent"]?: V}>`,
the mapped halves of pi's ThemeColorValues read off the island's theme
schema — was refused with SC8010 ("an island value of type … only primitives
and strings are copied"). The crossing classified values with
exportedByReference, which requires the object flag, so an intersection of
records looked like a value with no native representation even though
mapTypeOf maps it to the record its parts make.

The copy decision for a value crossing OUT is now copiedRecordType: the
object types exportedByReference names, and intersections of them (nullish
arms aside). Such a value crosses as the deep checked copy the record path
already uses, so a field that contradicts the declaration throws
`TypeError: expected string at $.fg, got number` instead of entering
natively typed memory (types don't lie). Copy, not view, for the reason
9a8e964 chose for arrays: nothing native can alias the island's object.

Test: tests/corpus/6899-node-island-unsafe-record (differential to Node,
plain and sanitized) and the lying-record case in
tests/harness/node-island-handles.test.ts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 19:14:36 -07:00
2026-10-29 16:39:31 -05:00
2026-10-16 10:33:14 -05:00
2026-10-29 16:39:31 -05:00
2026-10-14 17:27:02 -05:00
2026-10-29 06:02:00 -05:00
2026-07-22 18:08:04 -05:00
2026-10-25 21:21:26 -05:00
2026-07-22 18:08:04 -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
203 MiB
Languages
TypeScript 68%
C 23.2%
JavaScript 8%
C++ 0.7%