workerd has some eccentricities from it being tailored to the CF platform, so while it works fine(mostly) for local dev, and you can use it for production loads, I would probably recommend adding a service-worker or equivalent to your tool code so that it can keep itself running, rather than trying to wrangler workerd into working locally.
API interface.vitest-environment-miniflare, or maybe jest-environment-miniflare), and there should be a new variant that supports v3 
vitest-environment-miniflare setup until v3 supports it in some way - unit tests aren't currently possible - you can use unstable_dev from wrangler if you want to do e2eworkerd is released. workerdworkerdworkerdvitest-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.unstable_devimport { 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 drizzle