Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

denoflare serve: WorkerD support? #34

Open
JustinGrote opened this issue Dec 8, 2022 · 1 comment
Open

denoflare serve: WorkerD support? #34

JustinGrote opened this issue Dec 8, 2022 · 1 comment

Comments

@JustinGrote
Copy link
Contributor

JustinGrote commented Dec 8, 2022

Now that workerd is working reasonably well:
https://github.com/cloudflare/workerd

Should we add support to be able to start/watch it in the same way wrangler dev --experimental-local does? Since the APIs are emulated the same, it shouldn't matter if its deno or node style post-bundling using this worker.

@johnspurlock-skymethod
Copy link
Contributor

👍 I would love to have workerd as a local option for serve - good long-term goal.

First step would be to find/make a Deno package to manage workerd. It does not have implementations for any Cloudflare service APIs like KV, so we'd need a way to pass our implementations down for it to use.

Denoflare's default isolation mode already rpc-ifies these service APIs, so they can be threaded out through the permissionless isolate, and in preparation for a process-based isolation mode, once denoland/deno#10750 is implemented. This work might make remoting down to a separate workerd process a bit easier than starting from scratch.

Some of the missing features and sandbox warnings in the current workerd readme are also an indication to me that this might be a longer-term vision rather than a shorter-term viable project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants