[cramforce]

Stacked on #1458.

Summary

A project marks packages it never loads in its package.json, as "scriptc": { "packages": { "<name>": "unloaded" } }. require() and static imports of such a package fail with Node's MODULE_NOT_FOUND / ERR_MODULE_NOT_FOUND, exactly as when the package isn't installed, and the package never joins the program. Two shapes escaped that:

• A workspace package marked unloaded still resolved to its sources, so an import() of it compiled the package and its whole dependency graph. The workspace resolver now treats an unloaded name as missing. The import() rejects with Node's ERR_MODULE_NOT_FOUND ("Cannot find package '' imported from ").
• A module that only import() loads, whose static import names a package Node can't resolve (unloaded or absent), failed the build with SC1010. Node resolves that module's static graph when the import() runs, and rejects the promise before any module of the graph evaluates. Preflight now runs its existing resolution walk from each module reached only through a literal import(). When the walk finds a refusal, that import() rejects with Node's message and code, and the refused graph's modules never join the compiled graph or the npm selection. The refusals inside that graph no longer fail the build.

The rejection happens on a microtask after the call, as with any import(). Code that reads the namespace after await still compiles, typed dynamically, because the namespace is never produced. Refusals in the startup graph keep their behavior: the program compiles to Node's startup crash.

Evidence

• New npm case unloaded-dynamic-import. Both packages are missing under Node, which is the oracle:

  • an import() of an unloaded workspace package, with its namespace destructured;
  • an import() of a local module whose static import names an unloaded package.

  Each rejects with ERR_MODULE_NOT_FOUND and Node's message, and the local module's body never runs. Output is byte-identical to Node's.

• package-shims.test.ts has a new test that installs both packages: the workspace package linked into node_modules, and an ES module package. Node loads both, which is the control. The compiled program's output is unchanged from the missing-package run.

• Before this change, the same program failed to build with SC1010, and an installed unloaded workspace package was compiled and run.

• The existing unloaded-optional-dependency, dynamic-import, dynamic-import-local, workspace-* and workspace-dynamic-import-deps npm cases pass. The npm, npm-static and package-shims suites and the frontend unit tests pass 1106 of 1107; the one failure, node24-url-authority, comes from the sandbox's Node 24.15 versus the pinned 24.22.

• Zero-cost gate against Compile polyfill packages that are Node builtins as the builtins #1458's tip (8a40fb5, before its readable-stream 3.x commit, which this branch also carries): PASS. All 2502 programs (bench, self, corpus) are byte-identical; bench geomean is −0.18%.

• The self-hosted compiler builds (identical in the gate), and self-hosting-native-driver.test.ts passes (1155 s).

• pnpm lint, pnpm format:check and test:ts7 --baselines-only pass. Re-recording all order baselines adds only the new cases' entries.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
scriptc	Ready	Preview, v0	Oct 20, 2026 3:17pm UTC

[vercel]

When a literal import() targets a failing dependency of an already-rejected import graph, covered.has(root) skips its rejection entry, so the dependency is compiled and can fail lowering instead of rejecting at runtime.