With hyperdrive? Moving to #hyperdrive might make more sense here
With hyperdrive? Moving to #hyperdrive might make more sense here
d1 in the github repo linked in the docs, and it creates the db for testing using migrations. I expected to test my local d1 directly and this will know my local db from my bindings (toml is passed to vitest.config.mts).Internal error in D1 storage caused object to be reset.

npx wrangler d1 create to create a D1 database, he has to manually insert the new D1 binding configuration to the file wrangler.toml. However, if we execute this command in a folder that already contains wrangler.toml, can the binding insertion be achieved automatically, e.g. by a command option? If not, wouldn't this be a nice feature to implement?Internal error in D1 storage caused object to be reset. errors

import { env } from "cloudflare:test";
import { describe, it, expect } from "vitest";
import { Env } from "../src/index.js";
//This is in the docs for env
declare module "cloudflare:test" {
interface ProvidedEnv extends Env {}
}
it("Prepared statements", async () => {
//test some function that uses env, but doesn't query d1, and it works
...
//test some function which queries my local d1 db
// doesn't found the table/s used in my query, sql error.
const table_list = await env.MY_DB.exec("pragma table_list;");
console.log("Table list:", table_list);
// which prints: Table list: { count: 1, duration: 0 }
})npx wrangler d1 create