fix(module): keep extensions out of builtin inventory - #9934
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 8 included reviews per hour; 5 remain after this review. 📝 WalkthroughWalkthroughThe builtin resolver now keeps Perry’s ChangesBuiltin module resolution
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change removes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Landed on |
Perry added its
node:ffiextension to the shared dynamic-resolver allowlist, which also backsmodule.builtinModulesandModule.isBuiltin(). On the pinned Node 26.5.1 oracle that extension does not exist, so Perry exposed 67 entries instead of 66 and failednode-suite/module/exports/builtin-modules.Split Perry-only scheme modules from Node's public inventory.
node:ffiremains available through static imports,createRequire, andprocess.getBuiltinModule, whilebuiltinModulesandisBuiltin()now report the Node-compatible surface.Tracked by #9202.
Validation:
module/exports/builtin-modulesparity fixture (1/1)module/exportsparity group (5/5)node:ffiresolver probe: inventory false/false; resolver exports function/function/stringperry-runtimesuite (3,257 passed, 4 ignored; doc tests 8 ignored)./scripts/run_lint_gates.sh(all 64 local gates passed; 2 CI-only expressions skipped)Summary by CodeRabbit
Bug Fixes
node:ffiextension.node:ffiremains available when explicitly prefixed, while bareffiis not resolved.node:ffiis not included in builtin module listings orModule.isBuiltin()results.Tests