Seen more than one person mention this, trying to sus out if it's v3 related and how
Seen more than one person mention this, trying to sus out if it's v3 related and how

kj warnings are from workerd.miniflare@3/wrangler@3? I am able to get it to work on miniflare@2, however when migrating to wrangler@3, wrangler dev ignores the [miniflare] section in the wrangler.tomlFor Miniflare v3, we’re now using the industry-standard SQLite, with a separate blob store for KV values, R2 objects, and cached responses.
.wrangler folder again i do see those SQLite and blobs, was just partly hoping there's still a way for a redis support. Thanks!npm create cloudflare@2 and when starting it it raises the warn/error:2023-05-18 it should remove that message. You can also just ignore it.pages.dev domain. The staff use it to check their logsput: 'Value length of 39837727 exceeds limit of 26214400.'
kjminiflare@3wrangler@3wrangler@3miniflare@2[miniflare].wranglernpm create cloudflare@2[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-06-14". Falling back to "2023-05-18"...2023-05-18.pages.dev