CD
Cloudflare Developers•15mo ago
mattp

Incorrect type for Promise: the Promise did not resolve to 'Response'.

I'm using the itty-router for routing 
export default {
  fetch: async (request: Request, env: Env, context: Context) => {
    context.slack = new Slack(env.SLACK_APP_BOT_TOKEN);
    context.waitUntil(router.handle(request, env, context));
  },
};
export default {
  fetch: async (request: Request, env: Env, context: Context) => {
    context.slack = new Slack(env.SLACK_APP_BOT_TOKEN);
    context.waitUntil(router.handle(request, env, context));
  },
};
1 Reply
kian
kian•15mo ago
You're not returning any Response there Your fetch handler should return a Response or Promise<Response>
Want results from more Discord servers?
Add your server
More Posts
Orchestrate long running workers**Background information** I have a business use case that I'm trying to figure out how to implementDoes pages support Next.js rewrites?Does pages support Next.js rewrites in next.config.js?Can anyone help me understand and orCan anyone help me understand and/or convince my boss to use Cloudflare nameservers?hmm what specifically should I go turnhmm, what specifically should I go turn off?framework preset and build command keep changing randomlyI have an `Astro` website, I've set the framework preset 10 times, every time it changes to somethin🔌 Multiple Workers · MiniflareHi, I have a main worker which has service bindings to two other workers. I would like to create jes