mirror of https://github.com/vercel-labs/scriptc.git synced 2026-11-11 02:03:59 +08:00

Files

T

Malte UblandClaude Opus 5.5 b8ac5e3f6b Merge origin/main into opt/builtins-npm2

fs.constants as a value now builds its object from the fs group fill that
node:constants added (scr_fs_constants_object, defined after
scr_node_constants so the shared static keeps its place); the fallback
declarations gain the UV_FS_O_* Windows-only flags. Compatibility files
regenerated with pnpm manifest and pnpm node-compat.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-18 16:03:19 -07:00

generated

Merge origin/main into opt/builtins-npm2

2026-10-18 16:03:19 -07:00

src

Merge main

2026-10-15 21:48:48 -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

Merge origin/main into opt/builtins-npm2

2026-10-18 16:03:19 -07: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.