Cater for new local D1 database location

[dan-gamble]

Fixes #52

[mileszim]

@jplhomer can we get this merged in?

[mileszim]

@dan-gamble might be worth getting rid of this

[jplhomer]

For sure - @dan-gamble mind running pnpm run changeset and add a changeset so it triggers a release? It can be a minor release probably.

[stretch07]

@jplhomer can you merge this pls 🥺

superflare is literally awesome, I have yet to find anything like it to fit my needs ❤️

[dan-gamble]

@jplhomer I can't find any changeset scripts in the package JSON's? Am I being blind? 😅

[jplhomer]

@dan-gamble haha nope, my bad. Just npx changeset - I went ahead and added it. I'll update the repo with contrib instructions soon.

[jplhomer]

I'm getting DB Not found failures after this now 😢

[dan-gamble]

Tonight/this weekend I'll try spin up a new superflare app and see if I get that. If I do I'll try and work out what it was. Wrangler may have changed between when this was done and now

[dan-gamble]

Yea, it's super different now 🤔

[jplhomer]

Yeah... When I tried npx wrangler d1 create <name>, it created it in the path that Superflare used to think... but in addition to what was already set up with those three individual files? Very odd.

[dan-gamble]

I can see how the paths get created but I can't find a great deal on how the name/key for the DB is generated.

The only thing I could think to do at the moment is look for [state, v3, d1, miniflare-D1DatabaseObject] then just find the file that is just .sqlite. Doesn't feel great and I think if you had multiple D1 databases it'd like just put them all in this folder with different ID's so it's incredibly fragile