| Hi squaresmile, Thanks for the feedback! It sounds like you may be thinking of `wrangler preview`, not `wrangler dev`. `wrangler preview` runs the worker on a service that operates outside Cloudflare infrastructure, so a lot of things aren't realistic, like support for host+port and request.cf. `wrangler dev` runs the worker inside the real Cloudflare stack on the real edge, which should solve those problems. Our plan is to sunset `wrangler preview` in favor of `wrangler dev`. > It's not relevant now but I couldn't figure out how to connect cloudflared with wrangler tail on windows. Good news, this has been fixed recently -- `wrangler tail` no longer requires `cloudflared`. > - I haven't investigated this properly but Promise.then.catch doesn't seem to work? async/await works though. Promises are implemented inside V8, so they should work exactly the same on Workers as in Chrome and Node. I'd love to see an example of what's not working if you have one. > - I'm pretty sure URL.createObjectURL in this example [1] doesn't work on the worker. This is indeed an API we don't support, and realistically we probably can't support. I'd be interested to understand your use case for this. |
Ah sorry, I was confusing stuffs. It wasn't even wrangler preview, it was the web editor on the worker website.
> cloudflared
Yep, I noticed that update. I couldn't have updated wrangler faster.
> Promise.then
I'm sorry again. False alarm. It's me not understanding when things get executed.
> URL.createObjectURL
I don't really have a use case for it. It was mostly me seeing the example code being reasonable, copied it and was surprised it didn't work.