How would the local DX look like in this context? @smitssjors

I think CF pages works now as long as you don't use anything specific to CF,
miniflare still doesn't cover all the cases as well :(

@a-hariti It shouldn't have to be any different than it is now.

@smitssjors That's a terrible DX as it only works on the build output

you have to wait for a fresh build on each minute change

@a-hariti Yes I agree, but that is out of the scope of this issue. I think that fixing that would require substantial work on how adapters integrate with kit and vite. Currently they just adapt the output of building.

It could be an interesting idea to come up with something similar to how adapter node works. We could have a src/worker.ts file that looks something like:

import { handle } from 'some-virtual-module'

export default {
	fetch: handle
}

Though I only think this would work when deploying to workers right?

@ghostdevv To me this looks like a nicer solution. The node adapter docs are not clear where the custom server will live e.g., does kit copy over all files in src or does a user need to copy them over manually?

Though I only think this would work when deploying to workers right?

I think so.

+1

Sorry for resurrecting this issue, but I've got a use case which would greatly benefit from using queues as well as a scheduled worker.

Are there any further requirements for this beyond simply adding an option to the Cloudflare adapter which imports functions from a defined file and adds them to the generated worker?

If not, this seems fairly easy to implement, I might be able to put together a PR this weekend.

Other handlers don't seem to be supported for the Cloudflare Pages function. See #13207 (comment) and #13207 (comment)