oh because i saw this but i just checked it was for cloudflare pages
oh because i saw this but i just checked it was for cloudflare pages

RpcTarget doesn't have this.env. What am I forgetting?
wrangler, or via the GitHub/Lab integration?pnpm dlx wrangler pages deploy I can see that some JS files are indess above 1MB but below 10MBEmail Routing does not have advanced routing options. Characters such as + or ., which perform special actions in email providers like Gmail and Outlook, are currently treated as normal characters on custom addresses. More flexible routing options are in our roadmap.

Route pattern matching considers the entire request URL, including the query parameter string. Since route patterns may not contain query parameters, the only way to have a route pattern match URLs with query parameters is to terminate it with a wildcard, *.Is there a way to change this behavior to ignore the query string?
example.com/path and another example.com/path?*wrangler config then there is no way for it to be accessedworkers_dev = false when using a wrangler.tomlno-store request header in my Worker subrequests?



ctx.waitUntil() with a promise that manually resolves when the stream closes, and now I can do cleanup within that promise, but now I have no way to know that the client has disconnected and ctx.waitUntil() will just be aborted by the runtime 30s or so after the client disconnects.: comment) to test if the client is alive so that I can cleanup before that 30s elapses... is that correct? Any way to know immediately when a client has disconnected?await stream.write(...) rejects immediately if the client is disconnected, however if subclassing a ReadableStream, then controller.enqueue(...) does not throw and neither is underlyingSource.cancel() called when the client disconnects?example.com/pathexample.com/path?*workers_dev = falseno-storectx.waitUntil()ctx.waitUntil(): commentawait stream.write(...)ReadableStreamcontroller.enqueue(...)underlyingSource.cancel()