theswerd commented 1 month ago

I want to use deno_node without using deno_kv

The problem:

deno_node relies on deno_runtime
deno_runtime relies on deno_kv and deno_cron
Therefore I can't use deno_node without adding deno_runtime to my project

The good solution (I think/hope)

deno_node relies on import { kNeedsNpmProcessState } from "ext:runtime/40_process.js";, from what I can tell the only time this file is consumed is from deno_node. Therefore, I believe it can be extracted from deno_runtime, potentially added to deno_node.

I've added deno_kv and deno_cron as extensions to my setup, and just configured them with backends that don't do anything.

littledivy commented 1 month ago

deno_node relies on child process APIs from deno_runtime. We might want to extract that into it's own crate

RonnyChan-okta commented 1 month ago

Seconding this, we'd like to use deno_node without pulling in the entirety of deno_runtime.

bartlomieju commented 1 month ago

FYI even once this refactor this done you might not pull 2 or 3 deno_* crates that you'd have to pull right now.

RonnyChan-okta commented 1 month ago

Seems like it relies on runtime for console as well