D
vitest-environment-miniflare, or maybe jest-environment-miniflare), and there should be a new variant that supports v3 
S
E
M
D
vitest-environment-miniflare setup until v3 supports it in some way - unit tests aren't currently possible - you can use unstable_dev
Y
AM
Great question! Miniflare 3 only provides an implementation of the internal D1 API. Wrangler injects "shim" code into your worker to wrap this API into the regular D1 database API. There's an in-progress PR to move this "shim" out of Wrangler and into the runtime (https://github.com/cloudflare/workerd/pull/764), where it would be accessible to Miniflare. For now, your best bet is probably to just stay on Miniflare 2 until that PR is merged and a new version of 
workerd is released. A
HHHHHHD things will be a lot smootherH
HDHH
V
env.R2_BUCKET.put(key, request.body) you will get an error like "Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)".
TMTT
sourcemap support is on the docket for the API? That's pretty much the only bit of moving to v3 that's got me bummed, the logging leaves a lot to be desiredM
workerd, you'll need to wrap your worker with something that returns un-source-mapped stack traces as JSON using the MF-Experimental-Error-Stack header: https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/templates/middleware/middleware-miniflare3-json-error.ts. Wrangler will do this automatically.workerd at some point. TTwrangler.tomlunstable_dev() API (https://developers.cloudflare.com/workers/wrangler/api/) at some point soon, which will allow you to use your wrangler.tomlwrangler devesbuild watch -> MF reload script.Mwrangler devwrangler dev
TM
TTTtomlplacement table and had services below it, so services was interpreted as a key on placement)Tconsole.logs appear when running via the API, but they are appearing via wrangler devlog: new Log(LogLevel.VERBOSE), in my options and verbose: true,, is there something else I'm missing?vitest-environment-miniflarevitest-environment-miniflarejest-environment-miniflareCacheError [ERR_DESERIALIZATION]: Unable to deserialize stored cached data due to missing metadata.
The cached data storage format changed in Miniflare 2. You cannot load cached data created with Miniflare 1 and must delete it.import { D1Database, D1DatabaseAPI } from "@miniflare/d1";
import { drizzle } from "drizzle-orm/d1";
const d1 = new D1Database(new D1DatabaseAPI(sqliteDb));
const db = drizzle(d1); // now I can can write unit tests for drizzleworkerdworkerdworkerd/usr/lib/node_modules/wrangler/node_modules/@cloudflare/workerd-linux-64/bin/workerd: error while loading shared libraries: libc++.so.1: cannot open shared object file: No such file or directory
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above./usr/lib/node_modules/wrangler/node_modules/@cloudflare/workerd-linux-64/bin/workerd: error while loading shared libraries: libunwind.so.1: cannot open shared object file: No such file or directoryenv.R2_BUCKET.put(key, request.body)sourcemapMF-Experimental-Error-Stackunstable_dev()esbuildplacementplacementservicesservicesconsole.logslog: new Log(LogLevel.VERBOSE),verbose: true,