mirror of
https://github.com/vercel-labs/scriptc.git
synced 2026-10-28 06:53:42 +08:00
Malte UblandClaude Opus 5.5
18034065d6
A workspace package loaded on demand had its npm dependency selected, but the selection never scanned that dependency's own JavaScript: it is outside the startup module order, so a compiled CommonJS dist requiring a sibling package was refused with "the module is not supported yet". The scan of the import() graph now follows opted-in package JavaScript through its literal require() and import edges. The lowering appended those modules by their import declarations only, so a CommonJS file's requires never joined the compiled graph and their bindings stayed fenced. Preflight's resolved module edges, require edges included, now reach the walks that append import(), fork() and Worker modules, with lazy requires ordered after their module and inline require cycles answered as at startup. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>