Great! That would help a lot. One for deployments, but two also for local dev & mocking of bindings.
Great! That would help a lot. One for deployments, but two also for local dev & mocking of bindings.
(aswell integration with other build tools)
wrangler.toml like D1, but that's only for local dev—localwrangler kv:key put <name> <value> —binding <name of binding> —localkv:key part wrong but if you do wrangler —help then it should show the right command--live-reload--live-reload false and if that doesnt work, whats your wrangler version and workers/pages setup?yarn wrangler dev no longer works and crashes withnpx wrangler dev (after package manager installs it outside our project into home folder npm/npx cache), it seems to work but KV writes seem to crash with cryptic errors such as MINIFLARE_WORKERD_PATH I thinkwrangler dev on a project with a KV binding uses the preview_id from wrangler.toml. However, reading a value always returns null.--local writes it correctly to productionbetter-sqlite3 not being the right binary (don't remember the detail), so I did/.wrangler/state/v3/d1/{UUID}/db.sqlite for its sqlite storage/.wrangler/state/v3/d1/miniflare-D1DatabaseObject/{UUID}.sqlite <-- the UUID here, I have NO idea where it comes from and it is not in my wrangler.toml