[Deno] Path to stabilization

[lishaduck]

I plan on eventually PR'ing this to the main effect repo. Here's what I feel is needed first (TL;DR: Full Node compat):

Fill out DenoContext with Deno-native layers (Use of the Node compat layer is acceptable):

• Path (jsr:@std/path)
• CommandExecutor (Deno.Command) [🏃‍♂️ Add subprocess module #3]
• Terminal
• Worker (Web Workers)
• WorkerRunner (MessagePort) [Add WorkerRunner and tests for workers #5]
• FileSystem (Deno.* + jsr:@std/fs) [Add a Deno-native file system module #2]

Fill out additional documented platform primitives:

• KeyValueStore (Deno KV) [Deno KV #12]
• KeyValueStore (indexedDB) (There aren't any server impls anywhere)
• KeyValueStore (localStorage/sessionStorage) [Add localStorage and sessionStorage APIs #11]

Fill out HttpApi support:

• HttpClient (fetch())
• HttpServer (Deno.serve¹)

Ensure support for important² ecosystem packages:

• CLI (Just needs DenoContext?)
• RPC (Needs HttpServer)

Later:

• I haven't looked closely, but Permissions would probably be good to implement?
• Deno is adding otel, we should investigate integrating it

Footnotes

1. Should figure out how to support "declarative fetch"/deno serve via toWebHandler ↩

2. Read "packages I want to use, but would rather wait for Deno support first." ↩

[lishaduck]

Current status: DenoContext is almost done. I'm copying over the tests from the Node platform, finding bugs, fixing them, and repeating. Then, I'll just have DenoTerminal before I've finished milestone 1.

[nounder]

@lishaduck How is work in HTTP area? I'd like to help there.

[lishaduck]

@lishaduck How is work in HTTP area? I'd like to help there.

I've been busy with school and AoC for the last week, so I haven't gotten around to finishing work in KV; even then, I was planning on filling out the Terminal API and finishing up CommandExecutor first: in other words: work in http is lacking.
Feel free to send in a PR! I'd recommend trying to port HttpClient from effect-platform-browser. Speaking of which, I need to update the license to attribute Effectful Technologies...

Also, is there anything I can do to support effect-deno? I didn't look closely, but it looks like compat patches, so if there's anything I can do to help support it from over here, I'm happy to help.