-
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
process: move deprecation warning initialization into pre_execution.js #25825
Conversation
@@ -55,6 +56,7 @@ port.on('message', (message) => { | |||
if (manifestSrc) { | |||
require('internal/process/policy').setup(manifestSrc, manifestURL); | |||
} | |||
initializeDeprecations(); | |||
initializeClusterIPC(); | |||
initializeESMLoader(); | |||
loadPreloadModules(); |
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.
Is there any point in trying to group these 4 or 5 calls into a single one, possibly with an options object that indicates which parts of the setup to run?
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.
I've tried that before but a single call seems to hide too much details - I think it should be fine to directly drop some of the calls, for example, initializeClusterIPC
in repl.js
. Also the order in which these executes matters to some extent and an option object would blur that.
Maybe we could group them by different modes, but I cannot think of good names for those modes off the top of my head.
Since this is only necessary when user code execution is expected.
e137006
to
3f61246
Compare
Landed in 09a5f02 |
Since this is only necessary when user code execution is expected. PR-URL: #25825 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: James M Snell <[email protected]>
Since this is only necessary when user code execution is expected. PR-URL: #25825 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: James M Snell <[email protected]>
Since this is only necessary when user code execution is expected.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes