You cannot use the bun runtime on workers. I dont think you can really even import bun like that eve
You cannot use the bun runtime on workers. I dont think you can really even import bun like that even if you are using the bun runtime


resolveOverride today, to keep a Host header intact while changing the resolved origin address.
waitUntil() , scheduled handlers for workers, and for cron triggers, but none seem to mention what happens in an error case.waitUntil() although it does not state if there is any cascading of that rejection to anywhere outside the handler, or what might happen as a result of that. Would they appear in Cron events as a Status of Internal Error?
wrangler secret put <binding>resolveOverrideexport default {
async scheduled(event, env, ctx) {
ctx.waitUntil(Promise.reject('oh no'));
},
};waitUntil()waitUntil()wrangler secret put <binding>// Export a default object containing event handlers
export default {
// The fetch handler is invoked when this worker receives a HTTP(S) request
// and should return a Response (optionally wrapped in a Promise)
async fetch(request) {
// Parse the request URL
const url = new URL(request.url);
// If the request URL matches '/blog1', proxy it to the Cloudflare Pages site
if (url.pathname.startsWith('/blog1')) {
// Construct the proxied URL
const proxiedUrl = 'https://coderabbit-docs.pages.dev' + url.pathname;
// Proxy the request to the specified URL and return the response
return fetch(proxiedUrl, request);
}
// For other requests, return a default response
// return new Response('Welcome to my Cloudflare Worker!', {
// headers: { 'Content-Type': 'text/plain' },
// });
},
};Try again in 5 minutes. Your account is undergoing maintenance right now.