mirror of https://github.com/vercel-labs/scriptc.git synced 2026-10-31 07:23:06 +08:00

Files

T

Chris Tate 0e02fc28ca Accept mock.fn() without an original

node:test changes, matching Node 24.22:

- mock.fn() and t.mock.fn() without an original return undefined and
  record the arguments of each call, whatever the callers pass. The
  original and the initial implementation are a function that returns
  undefined, so restore() brings that function back.
- mock.fn<F>() with an explicit function type records F's parameters
  when F's return type is void or includes undefined. A return type
  without undefined, such as mock.fn<() => number>(), throws SC2020.

mock.fn()'s default type, (...args: any[]) => undefined, maps to the
checked-dynamic rest ABI used for program-declared (...args: unknown[])
functions: the calls log records the argument array, and the mock's
wrapper spreads it into the implementation.

A function whose fixed parameters are all unknown or any, or that has
none, now converts to a checked-dynamic rest signature without fixed
parameters, such as (...args: unknown[]) => void: each call passes the
arguments in order, undefined for the ones the caller left out. This is
how () => {} reaches mockImplementation and mockImplementationOnce, and
it applies to any such slot in TypeScript programs, which threw SC1090
before.

The mock-fn-default fixture and corpus program 5816 compare with Node,
plain and with SCRIPTC_SAN=1.

2026-10-19 16:59:05 -05:00

generated

Accept mock.fn() without an original

2026-10-19 16:59:05 -05:00

src

Derive the docs compatibility metadata at build time

2026-10-18 21:56:43 -05:00

node-v24.json

Move scriptc to Node 24.22.0

2026-10-14 17:27:02 -05:00

package.json

Make scriptc compilation native-only

2026-10-12 12:25:30 -05:00

README.md

Make scriptc compilation native-only

2026-10-12 12:25:30 -05:00

static-support.json

Accept mock.fn() without an original

2026-10-19 16:59:05 -05:00

README.md

Node compatibility ledger

This workspace package owns scriptc's Node.js parity system.

node-v24.json pins the Node release tag, commit, and canonical docs/source inputs.
static-support.json overlays dedicated compiler paths and their internal test evidence on the compiler's generated surface manifest.
generated/node-v24-internal.json is the engineering ledger, including implementation evidence and repository test paths.
generated/node-v24-backlog.json is the internal tier-specific work queue. It separates verification, implementation, explicit-refusal replacement, and partial-surface audit work, and prioritizes stable Node APIs above experimental, deprecated, and legacy APIs.
docs/src/generated/node-v24-compatibility.json is the stripped public artifact consumed by the docs website. It contains compiler-relevant runtime APIs, statuses, verification bases, and user-facing details; documentation, metadata, command-line/configuration entries, and rows that are N/A for native execution remain internal.

Statuses are evidence-aware: supported and partial require test evidence; refused requires an explicit compiler diagnostic or native throwing stub; not-implemented is the actionable backlog for an owned API family with no implementation match; by-design records an architectural exclusion; unreviewed still needs classification; and not-applicable is not a runtime API for that execution tier.

Run pnpm node-compat:backlog from the repository root for a summary. The filters --tier, --action, --priority, --chapter, and --status compose; use --format=json or --format=tsv for tooling.

Run pnpm node-compat from the repository root after changing the Node pin or the support manifest. pnpm node-compat:check is the offline drift/evidence gate; pnpm --filter @internal/compatibility check:upstream additionally verifies the pinned upstream inputs over the network.