(github.com)

30 points apatheticonion | 1 comments | 07 Sep 25 11:21 UTC | HN request time: 0.208s | source

Show context

laurencerowe ◴[10 Sep 25 06:23 UTC] No.45193982[source]▶

> To gain access to the Deno (and Node.js compat) standard library used by Deno requires forking deno_cli as they have largely coupled these additions to the main executable.

This is no longer the case. While it does not currently provide a stable API, that functionality exists in the deno_runtime crate and is relatively easy to reuse.

replies(1): >>45218066 #

1. apatheticonion ◴[12 Sep 25 02:26 UTC] No.45218066[source]▶

>>45193982 #

The deno_runtime crate is indeed easy to use however the exts that provide compat for web apis and Nodejs compat still require forking deno_cli. You can use some of their ext crates https://github.com/denoland/deno/tree/main/ext but not everything.

Also using ops within Workers is challenging, particularly if they share state.

↑

Show HN: Ion, a Rust/Tokio powered JavaScript runtime for embedders