Add `cfw.images` module

[ConProgramming]

The Cloudflare Images API is already great, but wrapping it with worktop might have some pros. For one it adds the types and lightweight api of worktop. Secondly though, using the cfw.kv module inside / with this module would make it simple to work with metadata and listing of images etc.

Ideally could be a very light be useful module. Just wraps some basic fetch calls to the images api and mixes in cfw.kv functions.

[lukeed]

Hey, thanks for the suggestion! Do you mind mentioning what use cases / methods you were imagining? Admittedly I haven’t used Images (yet) and agree this would be a good target module but I’m curious which APIs/actions are currently difficult to work with

[ConProgramming]

So I've been in the weeds with them for a few hours now haha:

1. No built in way to handle image metadata. This is super simple with kv of course but it seems like good low hanging fruit to be able to save / serve kv and images together as a common use case.
2. As noted elsewhere here, the upload response ids don't really correlate at all with the stored ids, so some route handler set to proxy uploads looks to be needed for any practical uploading. This is probably the most annoying thing.
3. Also, there's no way to list / search through images right now either. (A split by collection / tagging, would be super useful, because all of the cf images are unlabeled in one massive bucket) This is something else that's also pretty easy with kv but just would be great in a module.

I haven't touched deleting yet, but it looks to be like the serve api, which is also super simple (at least for public images). Even with these apis though, it'd be useful to have a TS lib and a more structured handle on them.

[ConProgramming]

Looking at this again, after some sleep, it might be better to just wait for R2 to come out and see how that will work out. Also, technically Cloudflare Images isn't worker specific, so not sure if it would fully make sense as a cfw submodule.