mirror of
https://github.com/vercel-labs/scriptc.git
synced 2026-10-28 06:53:42 +08:00
Malte UblandClaude Opus 5.5
700f59c1b2
T10 and T12 of the zero-cost compatibility plan, plus the maintainer decisions: - Programs that name Temporal type-check against TS 7's temporal lib (added only for them) and lower to Node 24's answers: typeof is "undefined", globalThis.Temporal is undefined, other uses throw ReferenceError at the root read. - node:v8 is importable; getHeapStatistics answers allocator-derived figures in Node's shape; other members fence with the by-design reason. vm's refusal says why. - node:stream/web exports the web stream globals themselves. - node:dns/promises and dns.promises: lookup and lookupService as promises, in the link-gated scr_dns_promises.c unit. - eval and the Function constructor throw Node's EvalError under --disallow-code-generation-from-strings; the corpus harness runs the Node oracle with that flag for `// @disallow-code-generation`. - graceful-fs is served as node:fs. Every new lowering replaces a refusal, and the new runtime code links only when used, so other programs compile to identical bytes (zero-cost gate). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 lines
879 B
Plaintext
2 lines
879 B
Plaintext
A compiled program embeds no JavaScript engine, so it cannot run JavaScript source at runtime. `eval`, indirect `eval`, `new Function`, and `Function` behave as they do under `node --disallow-code-generation-from-strings`, a deliberate difference from default Node.js: every call throws a catchable `EvalError` with the message `Code generation from strings disallowed for this context`. The arguments are evaluated first, and the Function constructor converts them to strings before it throws, as Node.js does. Packages that test for code generation before using it, such as zod 4, take their interpreted path. Code that needs to evaluate source at runtime must be rewritten; to compute a value from code at build time, use `comptime`. The `vm` module is refused for the same reason. See [npm Dependencies](/docs/dependencies#which-packages-compile) for which packages compile.
|