Chris Tate e4bd46c826 fs, net, dgram, tls, and stream misuse throws Node's validation ladders ...

- Per-API validators in the checked-dynamic lane run Node's argument checks in Node's order, then the real operation or a rendered fence thrown after validation
- fs.exists is genuinely async including the synchronous-false wart; mkdtempSync and lchmod are real
- Destructured sub-namespace bindings resolve as their module; function-armed unions cross into the checked-dynamic world
- dgram state errors carry their ERR_SOCKET codes

# Conflicts:
#	packages/compiler/test/ts7/baselines/order-parity.json

2026-07-24 08:07:01 -05:00

..

corpus

fs, net, dgram, tls, and stream misuse throws Node's validation ladders

2026-07-24 08:07:01 -05:00

coverage-fixtures

Coverage fixtures keep their loose-equality pins mixed-kind

2026-07-23 01:26:57 -05:00

deadstrip

init

2026-07-22 18:08:04 -05:00

diagnostics

Ambient roots trap whole chains; dead and nullish generic bindings lower to their runtime truth

2026-07-24 08:06:21 -05:00

fixtures

Routed operations over engine-held dyn values: keyed access, calls, method dispatch, and nullish tests

2026-07-24 07:59:12 -05:00

harness

Ambient roots trap whole chains; dead and nullish generic bindings lower to their runtime truth

2026-07-24 08:06:21 -05:00

library-mode

Library mode takes the static-or-refuse posture for bare npm specifiers

2026-07-23 21:07:29 -05:00