Your framework can give you access to bindings in dev via `getPlatformProxy`
Your framework can give you access to bindings in dev via
getPlatformProxygetPlatformProxy3.80.4 and running wrangler types results innpm create cloudflare@latest my-astro-app -- --framework=astro --experimental)--remote mode is kind of weird because it has to interact with prod services for stuff like R2known issue with fetch() requests to custom HTTPS ports in published Workers: the custom port will be ignored when the Worker is published using the "wrangler deploy" command.Waiting for DNS to propagate (36s) ... for like 15 min now, even though I can access the deployment already. Any idea what could the cause be?npm run deploy 
wrangler types add the generic "body" type for a Queue?npx wranger secret put foo. It opens up the cloudflare consent screen, but then when I click "allow", it hangs. Any thoughts?--test-scheduled working for folks in the latest version of Wrangler?--x-dev-env=false fix it?known issue with fetch() requests to custom HTTPS ports in published Workers: the custom port will be ignored when the Worker is published using the "wrangler deploy" command.3.80.4✘ [ERROR] EISDIR: illegal operation on a directory, readnpm create cloudflare@latest my-astro-app -- --framework=astro --experimental