I don't believe there's anyone who's received it yet

Propagation delay is now gone, new Worker updates will be live almost instantly again

yay! Nice job 🙂

oooo it looks like I got Hono + zod + zod-to-openapi working

Is there a way to get access to the cloudflare rendering api (puppeteer). I would like to switch away from browserless to cloudflare... anyone know how to get access? Already signed up for the waitinglist...

surprised I haven't seen someone else make an example

Just got to wait. AFAIK, it isn't even in private beta yet, so it might be a little while before it happens.

Got it! Will use browserless in the mean time in my workers

make one!

what's the feature list supposed to be? I have something similar to this on my TODO list I think

what is the currently recommended approach for testing? I see 2 different approaches and I am getting confused with multiple ways to simulate environments. I see miniflare with e.g. the

vitest-miniflare-environment

as well as the

unstable_dev

from wrangler? When should I use which approach? (I am trying to write an e2e test, that kinda touches DOs and D1)

And bonus points if I can mock outgoing http requests

Vitest would probably be best, as it supports hooking into the Vitest family of testing utilities, while

unstable_dev

just allows you to run

wrangler dev

without the CLI.

There are reasonable examples of using unstable_dev within wrangler's own tests - you can do a lot with just something like

msw

on npm

would both approaches work with D1? I think I played around with the vitest environment, and it complained about D1. Are both approaches under the hood using miniflare and the differences should not be that big, or are they generally different under the hood?

unstable dev does support d1, yes

and if you specify

local: true

in it's options, it will use miniflare

(though miniflare's test mocking stuff doesn't work with it yet)

so only

unstable_dev

in not local mode will properly support d1 at the moment?

is the d1 state in that scenario persisted through multiple sessions? or is it "clean" everytime I start it up again?

do static "bucket" assets count towards the worker size limits?

I'm guessing not..

No? D1 will work fine in either

For remote mode, it'll persist. For local mode, it'll persist if you tell it to

Are you referring to workers sites?

yep

That stores the assets in KV, so it won't impact the size of your worker beyond the small amount of code to actually provide the interface for interacting with your namespace

How do I avoid this issue?

[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p @miniflare/tre@3.0.0-next.12)

If you install it, it won't have to dynamically load it