🐛 Bug Report — Runtime APIs: bad error message related to durable objects SQLite API`

[cowlicks]

See this miniflare issue for more details.

I got this issue running my tests that used miniflare:

Error: SQL is not enabled for this Durable Object class. To enable it, change `new_classes` to `
new_sqlite_classes` within the 'migrations' field in your wrangler.jsonc or wrangler.toml file. If using workerd directly,set `enableSql = true` in your workerd config for the class. Note that this change cannot be made after the class is already deployed to production.

(coming from this workerd code)
I was not using wokerd directly, I was using new_sqlite_classes, and it was not for a class that had already been deployed.

Ultimately i had to pass useSQLite: true (note this is not enableSql=true) into miniflare (the isssue linked above describes the solution more).

Improving this error message will hopefully save futures users a lot of headaches!

Thank you,
Blake

[kentonv]

It sounds like you were using the Miniflare API directly to run workerd, which is somewhat unusual.

I don't think the error message can be expected to cover every possible way that you might be running workerd. The error covers the lowest-level way (running workerd directly) and also the most common way (using wrangler).

[cowlicks]

Using the Miniflare API like this is the recommended way to test workers-rs code. So it may be worthwhile to consider providing a more helpful way to debug this. It makes sense that workerd can't cover everypossible scenario. What are some other ways to improve this situation?