fwiw if you don't want to have to declare `Environment` for every handler, you can type the `export

fwiw if you don't want to have to declare

Environment

Environment

Environment

Environment for every handler, you can type the

export default

export default

export default

export default object literal

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

interface Environment {
  TOP_SECRET: string
}

interface Message {
  MY_EPIC_QUEUE_MESSAGE_INTERFACE_OR_WHATEVER: string
}

export default <ExportedHandler<Environment, Message>> {
  async fetch(req, env, ctx) {
    return new Response();
  },
  async queue(msg, env, ctx) {
    // do stuff
  }
}

kianOP•12/8/22, 2:58 PM

once you go ExportedHandler you can't go back

kianOP•12/8/22, 2:58 PM

ever since @mrbbot mentioned it

Kkian fwiw if you don't want to have to declare `Environment` for every handler, you c...

Isaac McFadyen•12/8/22, 7:04 PM

Wah, TIL

John Spurlock•12/11/22, 6:23 PM

Question about introducing beta queues into a production worker: Ideally I'd like to set up an existing production worker as a consumer of a new queue and slowly start throwing non-critical background jobs at it. Will this have any hidden effects or limitations on the behavior/ deployment/performance of the existing fetch handler/DO part of this worker in any way? Wouldn't want fetchfetch to be limited to a few colos for example, but totally fine if queuequeue is.

maguayo•12/12/22, 2:08 PM

I need to add 400 messages to the queue. However, adding that many messages is slow. I was trying to add one message at a time and then create a new message once the previous one is finished (inside the task). However, it broke after 5 times. Is there a limit to prevent infinite loops or something?

RRob There should not be any hidden effects or limitations on the existing fetch/DO h...

John Spurlock•12/12/22, 4:56 PM

Excellent, thanks - then I will definitely dip my toe into running non-critical work on queues in prod - too useful a building block to wait for GA

Matt Silverlock•12/12/22, 9:04 PM

We now allow 100 queues per account. This will continue to grow: need to wire up some additional dials first. Docs PR in-flight but the new limit is in effect now. https://github.com/cloudflare/cloudflare-docs/pull/7006

GitHub

queues: increase limit to 100 queues by elithrar · Pull Request #70...

We now allow 100 queues per account.
P.S: In the future we will support even more!
cc/ @deadlypants1973