🐛 BUG: Image resizing is not supported by `wrangler2 dev`

What version of Wrangler are you using?

0.0.17

What operating system are you using?

Mac

Describe the Bug

Any requests for a resized image passes through to the source image (returns “content-type: image/whatever”).

This is easily seen when requesting format=‘json’…

Is this due to wrangler2 using miniflare under the hood? I’m accustomed to this behaviour in local dev with miniflare, and have a “canary fetch” to a known-good image early in my debug handler to remind me of this situation…

I’m expecting that when I run wrangler2 dev, live image resizing will occur, as it does with wrangler1 dev

(BTW, my wrangler.toml for the env under test points to an enterprise enabled domain with image-resizing activated)

I couldn’t find any mention of “image” in the project, 2.0 milestone, or issues - hth!

Regards, ptim

[petebacondarwin]

BTW, as a related FR, I’d love to receive warning (maybe a response header?) if image resizing is not enabled - this had me super confused for a while 😃

#barrier-to-entry

By the way, I took at look at the headers returned from a request that was resized and I see these items that do not appear if the resizing did not happen:

"cf-bgj": "imgq:0,h2pri",
"cf-cache-status": "HIT",
"cf-resized": "internal=ok/m q=0 n=58 c=10 v=2022.3.3 l=104",

In the case where the resizing did not happen we only get:

"cf-cache-status": "MISS",

So I think you could use that as a marker for whether image resizing is turned on.

[threepointone]

although wrangler.toml has workers_dev = false, hitting B opened up https://wrangler2-repro-534.my-org-com.workers.dev/ - not sure if that’s expected - I don’t really use that functionality

We haven’t fleshed out proper support for zoned workers just yet, that should be incoming soon. Thanks for the report!

We should just fix the image resizing thing. Sorry about that, we’ll do it soon.