-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modules: do not share the internal require function with public loaders #26549
Conversation
|
||
const fn = compileFunction(id); | ||
fn(this.exports, requireFn, this, process, internalBinding, primordials); | ||
|
||
if (experimentalModules && this.canBeRequiredByUsers) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that since we no longer hits canBeRequiredByUsers
for the internal require
, we should be able to remove the immediate dependency of exposeInternals
in loaders.js
in a future PR, and get the value of that option from C++ later when necessary - only after bootstrap is complete, of course.
c880e16
to
e36dc52
Compare
This patch removes `NativeModule.require` and `NativeModule.requireWithFallbackInDeps`. The public loaders now have to use a special method `NativeModule.prototype.compileForPublicLoader()` to compile native modules. In addition this patch moves the decisions of proxifying exports and throwing unknown builtin errors entirely to public loaders, and skip those during internal use - therefore `loaders.js`, which is compiled during bootstrap, no longer needs to be aware of the value of `--experimental-modules`.
e36dc52
to
df42c60
Compare
Landed in 84156cf |
This patch removes `NativeModule.require` and `NativeModule.requireWithFallbackInDeps`. The public loaders now have to use a special method `NativeModule.prototype.compileForPublicLoader()` to compile native modules. In addition this patch moves the decisions of proxifying exports and throwing unknown builtin errors entirely to public loaders, and skip those during internal use - therefore `loaders.js`, which is compiled during bootstrap, no longer needs to be aware of the value of `--experimental-modules`. PR-URL: #26549 Reviewed-By: James M Snell <jasnell@gmail.com>
This patch removes `NativeModule.require` and `NativeModule.requireWithFallbackInDeps`. The public loaders now have to use a special method `NativeModule.prototype.compileForPublicLoader()` to compile native modules. In addition this patch moves the decisions of proxifying exports and throwing unknown builtin errors entirely to public loaders, and skip those during internal use - therefore `loaders.js`, which is compiled during bootstrap, no longer needs to be aware of the value of `--experimental-modules`. PR-URL: #26549 Reviewed-By: James M Snell <jasnell@gmail.com>
This patch removes
NativeModule.require
andNativeModule.requireWithFallbackInDeps
. The public loaders nowhave to use a special method
NativeModule.prototype.compileForPublicLoader()
to compile nativemodules. In addition this patch moves the decisions of proxifying
exports and throwing unknown builtin errors entirely to public
loaders, and skip those during internal use - therefore
loaders.js
,which is compiled during bootstrap, no longer needs to be aware of
the value of
--experimental-modules
.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes