Kevin Flansburg

> The original PR for the most part addressed this by creating `Send` wrappers around this types. Would that be an option? I'm just a little worried about having to...

> > I'm just a little worried about having to go through wrap every single type. It feels time consuming and error prone. This addresses the issue right at the...

> Hmm, I see how creating `Send` and `Sync` wrappers for the JS types can become quite complex. > > For advanced use cases like ours I think it's not...

I see, well I'm not opposed to implementing `Sync` / `Send` for specific types like `Env`, `Context`, and others (some of these changes have already landed), but in general I...

> Maybe the macro is the best solution after all. We'll have to `unsafe` implement `Send` and `Sync` for our app state (which I was hoping to avoid) but I...

Agree that these error messages aren't great. What does the error message look like if `axum`'s debug macro is used? I think they may already have done some work here....

Thanks for the detailed description. I think option 1 is most viable, but I will investigate 2 I believe it may just support the [standard Range header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests). Regarding the API,...

Which version of worker-build are you using? It sounds like Pages may not support the new WorkerEntrypoint interface introduced for RPC. Edit: are you supplying a custom JavaScript entrypoint script?

> @kflansburg > > Thanks. > > After changing the version of worker-build back to 0.1.0 everything is fine. > > Hopefully maybe the new WorkerEntrypoint interface could have some...

> I'm using this code as Cloudflare Pages Fucntions and it works fine with [email protected] + [email protected] > > @kflansburg Yes, what I'm saying is that the bug may not...