mirror of
https://github.com/vercel-labs/scriptc.git
synced 2026-10-21 05:50:55 +08:00
* feat(fs): expose Stats disk metadata - Lower blocks, nlink, and atimeMs through the C and LLVM backends. - Populate path, promise, file-handle, and dynamic bridge stats across supported platforms. - Add differential, declaration, and npm bridge coverage. Co-authored-by: I Plan Websites <787729+iplanwebsites@users.noreply.github.com> * fix(fs): keep Windows stats snapshots coherent * fix(fs): preserve Windows lstat metadata * fix(fs): validate Windows mount point payloads --------- Co-authored-by: I Plan Websites <787729+iplanwebsites@users.noreply.github.com>
node-types fixture
A project whose node_modules contains @types/node — the adoption path for real-world Node/TypeScript projects. The vendored node_modules are COMMITTED TEST DATA, pinned so the type surface (and therefore the pinned diagnostics) never drifts with the registry:
@types/node24.13.3undici-types7.18.2 (its dependency — declares the web-platform globals: fetch/Response/AbortSignal/ReadableStream/...)
What the fixture pins (see tests/harness/project-config.test.ts):
argv-env.ts— the SUPPORTED process surface (argv, env) typed by @types/node lowers statically and the binary runs: with @types/node present, the shipped fallback declarations forprocess/node:fs/consolestand down (their types come from @types/node), but the same members lower to the same libCalls, recognized by name + @types/node provenance.fenced.ts— surface @types/node DECLARES but scriptc does not lower (process.uptime, Buffer.from, setInterval) reports the SC2020-family fence naming @types/node, instead of typechecking its way into a broken binary — and never a raw "Cannot find name" error.
Projects WITHOUT @types/node (every other fixture and the whole corpus) keep the shipped fallback declarations and behave exactly as before.