createHash, createHmac, crypto.hash, pbkdf2, pbkdf2Sync, hkdf and hkdfSync accept every digest crypto.getHashes() lists in Node 24: SHA-512/224, SHA-512/256, SHA-256/192, SHA3-224 to SHA3-512, Keccak-224 to Keccak-512, SHAKE128, SHAKE256, KECCAK-KMAC-128, KECCAK-KMAC-256, RIPEMD-160, BLAKE2b-512, BLAKE2s-256, SM3 and MD5-SHA1. The new runtime unit scr_hash.c implements Keccak, RIPEMD-160, BLAKE2b, BLAKE2s and SM3, and is registered in both runtime pack matrices and the C-compile path. Names resolve as Node 24.22 resolves them: case-insensitively, with OpenSSL's provider aliases and object identifiers, ending at the first NUL, and with trailing spaces allowed except on the RSA signature aliases. "dss1" and "DSS1" are SHA-1, and createHash and crypto.hash accept "dss1" in any case. The compiler no longer refuses literal digest names outside SHA-1/SHA-2 and MD5; unknown names throw Node's errors at run time. SHAKE and KMAC digests use their default output lengths. createHmac rejects them with Node's OpenSSL error, pbkdf2 with "xof digests not allowed", and hkdf with "Deriving bits failed". pbkdf2 with a key length of 0 now fails with "Deriving bits failed" as in Node 24.22, and the callback forms pass these failures to the callback. PBKDF2 computes the keyed HMAC states once instead of on every iteration, and digest contexts are cleared with memset and a compiler barrier instead of a byte loop. The Keccak permutation, the RIPEMD-160 and BLAKE2 compression functions and the SM3 rounds are unrolled with constant indices.
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.