vercel-labs/scriptc：README 來源編輯指南

vercel-labs/scriptc 的 README 將專案描述為「TypeScript-to-Native Compiler」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「scriptc」下寫到：Zero-runtime TypeScript. scriptc compiles ordinary TypeScript into small, fast native executables , no Node, no V8, no JavaScript engine in the binary.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「What compiles」與相關條目，可以先判斷它是否處理你的實際問題：The standard library , strings with UTF-16-exact semantics, arrays/Maps/Sets with JS-exact ordering and identity, JSON with runtime-validated casts, Math, typed arrays and Buffer, Error hierarchies with typed catch.。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：The language , classes with single inheritance and true dynamic dispatch (devirtualized when provably safe), closures with JS capture semantics, generics (monomorphized), discriminated unions as tagged values driven by TypeScript's own。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「Install」等段落。可確認的線索包括：Requires clang (preinstalled with Xcode Command Line Tools). macOS arm64 is the primary platform; Linux and Windows binaries build by cross-compilation, each verified by its own differential test lane.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： $ cat fib.ts 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「Install」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「The idea: staticness you can see」段落提到：Most TypeScript is far more static than the ecosystem assumes. scriptc decides, construct by construct, what can compile to native code , and tells you:。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：Node's API surface , fs (sync and promises), path (byte-exact port), process, childprocess with piped streams, os, crypto, url/URL, zlib, timers and signal handlers on a dependency-free event loop , and the server stack: net, http, https,。