Malte UblandClaude Opus 5.5 9558fcddf3 Read Number.prototype and Boolean.prototype as prototype objects
A JavaScript source reading Number.prototype got undefined: the checker
types it with the wrapper interface, the type mapper maps that interface to
f64, and nothing built a prototype object.

The read now lowers, in JavaScript sources only, to dyn.builtinPrototype,
served by a new gated unit that builds the two prototype objects the way
the language defines them: an ordinary object on Object.prototype carrying
the kind's methods as non-enumerable, writable, configurable data
properties, answered from one box per thread so repeated reads are the same
object. A method runs on the prototype's primitive (+0 / false), which is
its [[PrimitiveValue]] in Node.

Two follow-on gaps the read exposed are fixed with it: narrowing no longer
extracts a scalar from a prototype value, and a call through the prototype
no longer takes the dyn.toString/dyn.valueOf/primitive-method
specializations, which assume a primitive receiver.

The methods are not generic: a receiver that is neither the kind's
primitive nor the prototype object — the wrapper around +0 / false, which
is its [[PrimitiveValue]] — is Node's TypeError, so a copied
`Number.prototype.toString` called on a plain object throws instead of
answering 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 05:38:57 -07:00
2026-10-27 23:21:09 -05:00
2026-10-28 20:50:23 -05:00
2026-10-16 10:33:14 -05:00
2026-10-27 23:21:09 -05:00
2026-10-14 17:27:02 -05:00
2026-10-25 11:26:13 -05:00
2026-07-22 18:08:04 -05:00
2026-10-27 16:45:14 -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
1 GiB
Languages
TypeScript 69.5%
C 21.3%
JavaScript 8.5%
C++ 0.7%