[@libsql/client-wasm] use sqlite3Worker1Promiser instead of sqlite3InitModule

[kwaa]

The current implementation runs in the main thread, making OPFS unavailable.

libsql-client-ts/packages/libsql-client-wasm/src/wasm.ts

Line 34 in fbf8f63

const sqlite3 = await sqlite3InitModule();

• https://github.com/sqlite/sqlite-wasm#in-a-wrapped-worker-with-opfs-if-available
• https://github.com/sqlite/sqlite-wasm#in-the-main-thread-without-opfs

[callum-gander]

Is there any plan to implement this? I've been playing around with libsql to potentially use in a production project due to the appeal of being able to more easily backup and sync with a remote version of the local db but libsql seems to basically have no persistence within the browser which wildly limits it in the browser and for browser extensions in particular. Compared to other language sdks and other platforms, e.g. node and deno, there seems to be next to no real investment in browsers.

I've tried using:

• kvvfs: this is mentioned here https://sqlite.org/wasm/doc/trunk/persistence.md#kvvfs yet this option won't work and produces errors that basically say query strings aren't allowed
• opfs: as outlined above, this doesn't seem to be working
• indexeddb: absurd-sql uses this https://github.com/jlongster/absurd-sql and it can also work

Honestly, it'd just be really nice to have any real option for persistent. Having to load the db in memory just doesn't work well for a browser extension, particularly as the DB increases in size