Divy

Marked as breaking because of the type definition changes. It should not affect runtime usage since we didn't guarantee `number | bigint` at runtime

Good catch. Did we ever use `kUint64` for `u64` return types though? We have some `needsUnwrapping` logic where its passes a mutable RV as the last value of the fast...

Maybe the temp directory Deno created got deleted before unzip was called. @flo-jan Do you have any background service that deletes `/tmp/`? The error message can be improved.

I'll close this issue because `Deno.run` is deprecated and will be removed in 2.0. Upgrade to `Deno.Command` API

@bartlomieju I'm not getting the IPC error. It fails on `.unref` ``` $ deno run -A --unstable-unsafe-proto npm:pm2 --help [PM2] Spawning PM2 daemon with pm2_home=/home/divy/.pm2 error: Uncaught TypeError: Cannot read...

Ah, I see the problem now. Our implementation only supports non-stdio IPC. We need to implement support for `stdio` as raw fds and "ipc" in `Deno.Command`. ```js const process =...

This should be straightforward to implement: - Add "ipc" (or maybe "ipc_for_internal_use") in `Deno.Command`'s stdin, stdout, stderr. Set the `args.ipc` FD and the ipc code path should automatically setup the...

stdio IPC support landed. A few more things to solve before this works: By default, pm2 spawns its daemon using node (hard-coded). The daemon fails to start in non-BYONM context...

Seems desirable. Reopening.

Spec issue: https://github.com/whatwg/websockets/issues/10