refactor: setup child process pipe in Rust (#21579)

Avoid passing the fd into JS and back into Rust. Instead we setup the
child's end of the pipe directly using a special Rust op.

1 files changed, 3 insertions, 1 deletions

diff --git a/ext/node/polyfills/child_process.ts b/ext/node/polyfills/child_process.ts
index c7d007f46..da82546f6 100644
--- a/ext/node/polyfills/child_process.ts
+++ b/ext/node/polyfills/child_process.ts
@@ -49,6 +49,7 @@ import {
 } from "ext:deno_node/internal/util.mjs";
 
 const { core } = globalThis.__bootstrap;
+const ops = core.ops;
 
 const MAX_BUFFER = 1024 * 1024;
 
@@ -822,7 +823,8 @@ export function execFileSync(
   return ret.stdout as string | Buffer;
 }
 
-function setupChildProcessIpcChannel(fd: number) {
+function setupChildProcessIpcChannel() {
+  const fd = ops.op_node_child_ipc_pipe();
   if (typeof fd != "number" || fd < 0) return;
   setupChannel(process, fd);
 }