fixup! fixup! bootstrap: support more builtins in the embedded code c…

…ache

lib/internal/bootstrap/node.js

@@ -6,7 +6,7 @@
 //
 // This file is expected not to perform any asynchronous operations itself
 // when being executed - those should be done in either
-// `lib/internal/bootstrap/pre_execution.js` or in main scripts. The majority
+// `lib/internal/process/pre_execution.js` or in main scripts. The majority
 // of the code here focuses on setting up the global proxy and the process
 // object in a synchronous manner.
 // As special caution is given to the performance of the startup process,
@@ -28,7 +28,7 @@
 // Then, depending on how the Node.js instance is launched, one of the main
 // scripts in `lib/internal/main` will be selected by C++ to start the actual
 // execution. They may run additional setups exported by
-// `lib/internal/bootstrap/pre_execution.js` depending on the runtime states.
+// `lib/internal/process/pre_execution.js` depending on the runtime states.
 
 'use strict';
 

lib/internal/main/mksnapshot.js

@@ -114,7 +114,7 @@ function requireForUserSnapshot(id) {
 function main() {
   const {
     prepareMainThreadExecution
-  } = require('internal/bootstrap/pre_execution');
+  } = require('internal/process/pre_execution');
 
   prepareMainThreadExecution(true, false);
 

lib/internal/wasm_web_api.js

@@ -15,7 +15,7 @@ function lazyUndici() {
 
 // This is essentially an implementation of a v8::WasmStreamingCallback, except
 // that it is implemented in JavaScript because the fetch() implementation is
-// difficult to use from C++. See lib/internal/bootstrap/pre_execution.js and
+// difficult to use from C++. See lib/internal/process/pre_execution.js and
 // src/node_wasm_web_api.cc that interact with this function.
 function wasmStreamingCallback(streamState, source) {
   (async () => {